-
-
Notifications
You must be signed in to change notification settings - Fork 112
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(web): drops alignInputs, hideInputs 📴 #7360
Conversation
User Test ResultsTest specification and instructions User tests are not required |
1c28631
to
e579530
Compare
5825921
to
897d3d7
Compare
e579530
to
d1887a5
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking good. I think we can go a couple of steps further, removing more util code, which maketh me happy!
web/source/kmwbase.ts
Outdated
// Legacy API function for touch-alias issue workarounds | ||
// Touch-aliases have been eliminated, though. | ||
['alignInputs'](eleList?: HTMLElement[]){} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why are we keeping this here? Is it just because it was a published and documented API?
In this situation, we then need a PR against the documentation to mark it as deprecated, so it can be removed in a future version.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
After a bit more investigation into any possible extra avenues for cleanup, I've documented #7387. It's not 100% straightforward, so it should probably be left out of this PR. |
…web/drop-alignInputs
Changes in this pull request will be available for download in Keyman version 16.0.82-alpha |
A follow-up to #7343.
I could've included it as part of that one, but these changes were easy enough to isolate and may be worth some discussion in isolation, given the old
waitForFonts
method. It is my understanding thatwaitForFonts
existed to prevent a "flash of unstyled content" effect on touch-alias elements that would otherwise result from asynchronous font loads.@keymanapp-test-bot skip