Closed
Bug 1164349
Opened 9 years ago
Closed 9 years ago
css not obeying to changing :target selector
Categories
(DevTools :: Responsive Design Mode, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1145010
People
(Reporter: public, Unassigned)
Details
Attachments
(1 file)
445 bytes,
text/html
|
Details |
User Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Firefox/38.0 Build ID: 20150505103531 Steps to reproduce: - navigate to www.internetseiten-vom-fachbetrieb.de - resize viewport to match css media queries for mobile devices - click the button in the header (to the left of "Internetseiten vom Fachbetrieb") - now click the "X"-button in the navigation to close it Actual results: the "X" in the navigation removes the "#top" from the url but the navigation bar did not close like it did in 37 Branch. Expected results: navigation should be closed by removing #top:target rule and resetting the "width"-attribute of "#nav .ym-hlist" to 0.
Reporter | ||
Comment 2•9 years ago
|
||
Try it with the following code: 8<----------------------------------8< <html> <head> <meta charset="utf-8"> <title>test case</title> <style> #top:target .content { background: #ff0000; } </style> </head> <body id="top"> <a href="#top"><button>set color</button></a> <a href="#"><button>clear color</button></a> <div class="content"> <p>This is some content.</p> <p>Bliblablu blubeldiblub blabla.</p> </div> </body> </html> 8<----------------------------------8< The "clear color" button should remove the red background from ".content". At least it did with Firefox prior to branch 38.
Flags: needinfo?(public)
Reporter | ||
Comment 5•9 years ago
|
||
Tested again and got some further information: Had the web development panel open to simulate different viewport sizes and if I close the development panel it also WFM.
Updated•9 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Component: Untriaged → Developer Tools: Responsive Mode
Resolution: --- → DUPLICATE
Updated•6 years ago
|
Product: Firefox → DevTools
You need to log in
before you can comment on or make changes to this bug.
Description
•