If you are working on US Department of State website, or knows someone who does, please let me know. There are issues specific to Safari browser which are easy to avoid, and some which affects any browsers. Both for https://ceac.state.gov/ and https://travel.state.gov/
A reminder that #CSSnesting is still a working draft in the #W3C under the #CSSWG. Please mind #webcompat when using this relatively new feature. IOW, don't make your #CSS break because you assumed everyone right now is using the latest version of #Chrome / #Chromium, #Firefox, #Safari, or #Edge. They might not even be using a mainstream #browser to visit your website (I am using #PaleMoon for example)... :seija_coffee:
I'm gathering information (and thoughts) on #i18n for a piece I'm going to write, and I wonder if or how Internationalization aspects factor in the #WebCompat activities and processes in place at browser vendors.
I‘m writing some documentation for better site-integrating with :vivaldi_red: #VivaldiBrowser-specific features for web developers. Anything you‘d like to see documented? My list so far includes Tab Notifications, Fast Forward, Accent Theme Colors, and more. #devRel#webDev#webCompat
@mozilla with the Mozilla Webcompat team is the main steward of the project, but #webcompat#bugs for websites breaking in any browsers, any devices are welcome.
Please, webdevs don't do user agent sniffing for activating the shim of a feature which can be… feature detected.
It kind of prevent your site of using the native feature when it's finally implemented in the browser. Sometimes it might even have performance impact for the users of your site. #webcompat
Doing #webcompat work on big $NAME website/app is like unclogging the P-TRAP of a kitchen sink.
Pull a thread and you think "That's it!", and then you realize there is a bigger mass attached to it, with grease, hair, and plenty of things you don't want to know about, and you discover more things down the line, plastic bits, a dead bug, etc.