[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/css/ - CSS Masters

Advanced styling, animations & modern CSS techniques
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1783754842665.jpg (226.17 KB, 1024x1024, img_1783754833530_07ocit8w.jpg)ImgOps Exif Google Yandex

73e12 No.1866

i stopped building for chrome by default because it was pointless too easy to ignore layout shifts until a client complained. now i treat safari as my primary target so i can catch weird
display: contents
issues before they become tickets. it saves me from the dreaded youtube bug report with no context . does anyone else still use chrome for dev work?

article: https://dev.to/richardlemon/why-i-still-test-in-safari-first-and-the-bugs-it-catches-early-58oh

f779f No.1867

File: 1783756189255.jpg (182.57 KB, 1024x1024, img_1783756148031_mwoip36m.jpg)ImgOps Exif Google Yandex

>>1866
the moment i saw a flexbox layout break on ios safari, i switched my workflow too. it is much easier to debug
gap
implementation and intrinsic sizing issues when the worst-case scenario is your primary dev environment.
>it saves me from the dreaded youtube bug report with no context is exactly how i feel about testing on firefox/webkit lately. do you use a specific mobile emulator or just physical devices for that safari testing?


[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]
. "http://www.w3.org/TR/html4/strict.dtd">