--- title: Browsers Treat Big Sites Differently | daily.dev description: Safari and Firefox ship domain-specific code that changes how certain websites render — a practice called 'quirks' or 'interventions.' WebKit's Quirks.cpp and... canonical: https://daily.dev/posts/browsers-treat-big-sites-differently-hldbesd4b twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Browsers Treat Big Sites Differently | daily.dev og:description: Safari and Firefox ship domain-specific code that changes how certain websites render — a practice called 'quirks' or 'interventions.' WebKit's Quirks.cpp and... og:url: https://daily.dev/posts/browsers-treat-big-sites-differently-hldbesd4b og:image: https://api.daily.dev/og/posts/HlDBeSD4B.png og:image:alt: Browsers Treat Big Sites Differently og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Browsers Treat Big Sites Differently **[Lobsters](https://daily.dev/sources/lobsters)** · 9 min read · 8 upvotes · 1 comments ## Summary Safari and Firefox ship domain-specific code that changes how certain websites render — a practice called 'quirks' or 'interventions.' WebKit's Quirks.cpp and Firefox's WebCompat system contain thousands of lines of if-domain-then-fix logic targeting sites like TikTok, Netflix, Instagram, Amazon, and even SeatGuru. These workarounds exist because developers build primarily for Chrome, which dominates with 80%+ market share, leaving other browsers to either break or silently patch popular sites. Chrome doesn't need a quirks file because the web is already built to match Chrome's behavior. The post argues this mirrors the old IE-era problem, just with a different dominant browser, and urges developers to regularly test in Firefox and Safari rather than relying on invisible browser-side fixes. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Community discussion Top comments from developers on daily.dev. **@petermrozek** · 0 upvotes > Huh... That's interesting. I'm building mostly for Firefox with a quick glance on Chrome to check if it looks ok. I even recently found out Chrome isn't keybord friendly. > > For instance, you can't Tab your way into a container element that has scrollbars (overflow set to auto or scroll) to scroll the content with the keyboard. That's something Firefox handles out of the box, while Chrome needs a CSS fix (artificial tabindex added on the container). > > You find interesting things when your choices are different that those of most people. 😉 ## Similar posts on daily.dev - [Your Browser Probably Lies To The Big Sites \(Blame Chrome\)](https://daily.dev/posts/your-browser-probably-lies-to-the-big-sites-blame-chrome--q7aefturi) · Hackaday · 17 upvotes · 2 comments - [New to the web platform in July](https://daily.dev/posts/new-to-the-web-platform-in-july-pfpy0b4gh) · web.dev · 0 upvotes · 0 comments - [Firefox for Web Developers: "Chrome looks set to ship an LL…"](https://daily.dev/posts/firefox-for-web-developers-chrome-looks-set-to-ship-an-ll--wdczuohwk) · Lobsters · 1 upvotes · 0 comments - [WebKit supports interactive-widget … and hopefully Safari will too?](https://daily.dev/posts/webkit-supports-interactive-widget-and-hopefully-safari-will-too--hig21dyrd) · Bram.us · 9 upvotes · 3 comments - [I tried using one browser for work and another for everything else, and it fixed a problem extensions never did](https://daily.dev/posts/i-tried-using-one-browser-for-work-and-another-for-everything-else-and-it-fixed-a-problem-extension-stloevi75) · XDA Developers · 4 upvotes · 5 comments --- Tags: [#webdev](https://daily.dev/tags/webdev), [#google-chrome](https://daily.dev/tags/google-chrome), [#firefox](https://daily.dev/tags/firefox), [#safari](https://daily.dev/tags/safari) [View this post on daily.dev](https://daily.dev/posts/browsers-treat-big-sites-differently-hldbesd4b) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Browsers Treat Big Sites Differently","url":"https://daily.dev/posts/browsers-treat-big-sites-differently-hldbesd4b","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/browsers-treat-big-sites-differently-hldbesd4b"},"datePublished":"2026-05-14T13:34:13.932Z","dateModified":"2026-05-14T13:34:40.299Z","description":"Safari and Firefox ship domain-specific code that changes how certain websites render — a practice called 'quirks' or 'interventions.' WebKit's Quirks.cpp and...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/e7eb873770444075e3273a8fa687f48d?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/e7eb873770444075e3273a8fa687f48d?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Lobsters","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Lobsters","logo":"https://media.daily.dev/image/upload/s--tl8v_Fku--/f_auto,t_logo/v1698841318/logos/lobste.jpg","url":"https://daily.dev/sources/lobsters"},"commentCount":1,"discussionUrl":"https://daily.dev/posts/browsers-treat-big-sites-differently-hldbesd4b","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":8},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":1}],"keywords":"webdev,google-chrome,firefox,safari","timeRequired":"PT9M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Lobsters","item":"https://daily.dev/sources/lobsters"},{"@type":"ListItem","position":3,"name":"Browsers Treat Big Sites Differently"}]} {"@context":"https://schema.org","@type":"WebPage","@id":"https://daily.dev/posts/browsers-treat-big-sites-differently-hldbesd4b","comment":[{"@type":"Comment","text":"Huh… That’s interesting. I’m building mostly for Firefox with a quick glance on Chrome to check if it looks ok. I even recently found out Chrome isn’t keybord friendly.\nFor instance, you can’t Tab your way into a container element that has scrollbars (overflow set to auto or scroll) to scroll the content with the keyboard. That’s something Firefox handles out of the box, while Chrome needs a CSS fix (artificial tabindex added on the container).\nYou find interesting things when your choices are different that those of most people. 😉","datePublished":"2026-05-15T07:58:50.146Z","url":"https://daily.dev/posts/HlDBeSD4B#c-QwVN4XznA","author":{"@type":"Person","name":"Peter Mrożek","url":"https://daily.dev/petermrozek","image":"https://media.daily.dev/image/upload/s--pBfYX68K--/f_auto/v1769247960/avatars/avatar_Qz65P1nVw3Bu6C5YwaZgA?_a=BAMAMiiu0"}}]} ```