"-internal" pseudo-elements are not applying
Reported by
oli...@xteach.es,
Oct 30
|
|||||
Issue description
UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.181 Safari/537.36
Steps to reproduce the problem:
1. Set the following CSS class:
video::-webkit-media-controls-overflow-button {
display: none;
}
2. Open the view with a video
3. Class is not aplying
What is the expected behavior?
CSS should apply
What went wrong?
After a research I found a previous issue ( https://bugs.chromium.org/p/chromium/issues/detail?id=678285 ) where the -internal pseudo-elements were removed.
The trouble is that video shadow elements in native player (among others) still have those pseudo classes.
I guess that those pseudo classes should switch to webkit or other that will work.
Did this work before? N/A
Does this work in other browsers? N/A
Chrome version: 71.0.3578.20 Channel: beta
OS Version: Ubuntu 16.04
Flash Version:
,
Oct 30
In 70.0.3538 happens as well
,
Oct 30
,
Oct 31
oliver@ Thanks for the issue. Request you to provide a sample file where this issue can be reproduced, which will help in further triaging. Thanks..
,
Oct 31
I created a basic fiddle to show what I am talking about https://jsfiddle.net/5gtjvmhw/ The three-dots button should be hidden, but the pseudo-class does not apply because -internal pseudo-elements were deprecated. The trouble is that native video player is still using them. As said previously this happens in 70+ versions.
,
Oct 31
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 1
::-internal-* pseudo elements are named so because they are intended to be for internal use only. We have tried to remove non-standard ::-webkit-* to the extent possible based on usage data. Some ::-webkit-* pseudos are still present for web-compat. If there is real need to style internal components like this, it should be done in a non-vendor-specific way through CSS specs. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by dtapu...@chromium.org
, Oct 30