On Friday 2016-11-25 02:09 +0800, Chih-Hsuan Kuo wrote: > It means the browser engines can use the properties, but these properties > don't accept any value. It also means the properties don't work. > > > In Google Chrome, these properties can be auto-completed. And the error shows > when we set the value to these properties. > > > In Safari, there is no warning symbol on these properties, and the warning > symbol only shows on the value we set.
So my impression is that you're looking to implement these unstandardized properties because of Web compatibility risk. If you're analyzing that risk, it doesn't matter what developer tools do. What matters is whether the presence of the properties in Web content does something that we also need to do if we want the content to behave in the same way. I can't tell from your comments which other browsers do this. -David -- 𝄞 L. David Baron http://dbaron.org/ 𝄂 𝄢 Mozilla https://www.mozilla.org/ 𝄂 Before I built a wall I'd ask to know What I was walling in or walling out, And to whom I was like to give offense. - Robert Frost, Mending Wall (1914)
signature.asc
Description: PGP signature
_______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
