RESOLVED CONFIGURATION CHANGED 142737
text-decoration in a:not(:link):not(:visited) rule affects <a href> elements
https://bugs.webkit.org/show_bug.cgi?id=142737
Summary text-decoration in a:not(:link):not(:visited) rule affects <a href> elements
Adam Roben (:aroben)
Reported 2015-03-16 11:06:36 PDT
1. Go to data:text/html,<style>a:not(:link):not(:visited) { text-decoration: none }</style><a href="#">should be underlined</a> In Chrome and Firefox, the text is underlined. In Safari 8.0.3 on Yosemite, it is not. (I haven't tested other versions/OSes.) Interestingly, the bug does not occur for other CSS properties, like color: data:text/html,<style>a:not(:link):not(:visited) { color: red }</style><a href="#">should be blue</a> Maybe this is somehow related to https://bugs.webkit.org/show_bug.cgi?id=142734, though it would be a little surprising since that bug is about styles *not* matching, while this bug is about styles applying when they should not.
Attachments
Adam Roben (:aroben)
Comment 1 2015-03-16 11:33:28 PDT
Looks like this is not a bug in the r181548 nightly build. I wonder when it was fixed?
Benjamin Poulain
Comment 2 2015-03-16 11:38:37 PDT
(In reply to comment #1) > Looks like this is not a bug in the r181548 nightly build. I wonder when it > was fixed? My guess is it was not fixed :) It looks like a bug in the way we computed the link-state of selectors. When we disabled :not(:visited), we hid this bug.
Adam Roben (:aroben)
Comment 3 2015-03-16 11:40:48 PDT
Also not a bug in r179145. I tried r160979 but it won't launch on Yosemite.
Ahmad Saleem
Comment 4 2022-07-24 11:48:24 PDT
I am not able to reproduce this bug using Comment 01 test case in Safari 15.6 on macOS 12.5. I changed the test case into following JSFiddle - https://jsfiddle.net/n2yqk4pw/show It is showing 'underlined' text and it is same across all other browsers (Chrome Canary 106 and Firefox Nightly 104) and Comment 03 also show it as being fixed, so I think we can mark this as "RESOLVED CONFIGURATION CHANGED". Thanks!
Note You need to log in before you can comment on or make changes to this bug.