Hello Firefox devs,
I am Yash Joshi, an undergrad student from India. I recently wrote my first web platform test which checks if browsers wait for delayed stylesheets with non matching Media Queries. Every Single browser I tested [chromium safari and firefox] has not yet implemented the said feature.
I thus wrote a simple WPT which basically delays serving the stylesheet {with non matching MQ} by 1s and checks if browser continued JS execution in the meantime or waited for the stylesheet to load [test failed in this case] and all browsers fail test [expected] and firefox somehow passes this [which should not be the case].
I am attaching relevant links and detailed context below for your reference. Pls let me know what am I missing here or if there is something wrong with my approach.
Also, pls direct me to correct channels if this is not the right place to discuss this.
Thanks a lot for your consideration.
-------------------------------------------------------------------Details------------------------------------------------------------Relevant Specification: Assigning property values, Cascading, and Inheritance (w3.org) and CSS Cascading and Inheritance Level 5 (w3c.github.io)
Live Test Link (wait for 10s to load): and check the console panel for wait time : : https://cheerful-capybara-92469b.netlify.app [Source Code: Github Link for test code]
WPT Status : web-platform-tests dashboard (wpt.fyi)
Github Link: Add WPT to check that browser lazy loads non-matching Media Query by chromium-wpt-export-bot · Pull Request #38370 · web-platform-tests/wpt (github.com)
--
Gerrit Link: Add WPT to check that browser lazy loads non-matching Media Query (4224891) ·] Used trickle pipe for delay of 1s.
You received this message because you are subscribed to the Google Groups "firef...@mozilla.org" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firefox-dev...@mozilla.org.
To view this discussion on the web visit https://groups.google.com/a/mozilla.org/d/msgid/firefox-dev/9aaf45d3-39c9-4a09-9129-d482c8606664n%40mozilla.org.
Hi Yash, thanks for reaching out.Moving the thread to dev-platform@ which is the right mailing-list for Gecko stuff, and cc'ing Yoav who reviewed the chromium patch.So, what might happen (and pretty sure happens) is that we really start fetching the @import rule earlier than the first script runs, due to the import scanner that runs during parsing, introduced in bug 1546783.
You received this message because you are subscribed to the Google Groups "dev-pl...@mozilla.org" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dev-platform...@mozilla.org.
To view this discussion on the web visit https://groups.google.com/a/mozilla.org/d/msgid/dev-platform/CAFhp-qf5RWjh3TbNZ%3DsTOUk2xwnY2V1DOpLhcAG%3Dwhn0bHSYVg%40mail.gmail.com.