Add -webkit-tap-highlight-color #6473
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ghost
added
the
data:css
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This feature has a complex history. It required quite a bit of research to track down. Part of mdn/sprints#3436.
For posterity, I've cleaned up my notes below but here's the summary:
The story
Apple appears to have implemented this as a wholly proprietary feature for Safari for iOS in mid-2010. I can find GitHub commits and blog posts mentioning it as far back as June 2010, but no earlier. This suggests the feature was first made public in iOS 4.0 or 4.1. I've gone with the older value. On macOS, I think the feature has never been enabled. It doesn't tab complete in the developer tools, it's not recognized if you type it out manually, and Apple has never shipped a touch-enabled macOS device anyway.
In October 2011, the feature was added to WebKit proper, gated by a touch events flag that WebKit's downstream users could opt-in to. Based on some Chromium-specific commits to WebKit tweaking this feature, I think Chrome opted in to this very early on. Based on the date of the WebKit commit, I've guessed that this happened in Chrome 16 though it's possible this happened a little earlier or later (as early as 15, but no later than Chrome 26, the earliest I could check). This value is a guess, but it's pretty good one for a feature that's a decade old.
The other browsers were relatively easy. IE11 does not recognize the property nor provide tab completion for it in the inspector; Edge does from Edge 13 (the earliest I could test). Given that Edge added support for a number of
-webkit-prefixed features from the outset (12), I'm inclined to think this was supported from Edge's beginning.Firefox shows no evidence of having supported it. The remaining browsers I derived from Chrome.