Jeu 01 novembre 2018 by Karl Dubost (Worked at Mozilla from 2013 to 2022) Identifying the origin of the issue On webcompat, we try to diagnose bugs reported about sites, we do not have the original sources. If we are lucky, web developers have included a way to reach the original JavaScript source files (through sourcemap). But modern websites have often a series of optimization layers (with multi

I have seen clever, thoughtful and hardworking people trying to be right about the CSS is not broken and CSS is broken. PopCorn. I will not attempt to be right on anything in this post. I'm just sharing a feeling. Let me steal the image from this provocative tweet/thread. You can also read the thread in these tweets. I guess looking at the image I understood how/why the discussions would never hav

Mer 25 janvier 2017 by Karl Dubost (Worked at Mozilla from 2013 to 2022) Ok, Houston, Mozilla, we've had a problem here. We (Dennis, Eric and Mike from the webcompat team) recently released a new button in Firefox Nightly: Report Site Issue. The button who was previously available in Firefox Nightly Android is now available on Firefox Nightly Desktop. The button intent is for the users: help them

Ven 06 janvier 2017 by Karl Dubost (Worked at Mozilla from 2013 to 2022) Welcoming a new webcompat team member, Ola on our webcompat teleconf. The Japanese engineering team has moved to a new office near Tokyo station. A lot less fancy than the beautiful space near National Arts Center, but a new space for discovery and exploration. webcompat issues Yet another regression related to the combinatio

Yesterday, I have written about the strange value of the CSS width when set with a percentage. One Japanese night later, Boris Zbarsky sent me a private email explaining how CSS widths are computed in Gecko. These short emails are a gem of pleasure to read and insights into Gecko. I should almost open a new category here called "Santa Boris". I love them. Thanks. So what did I learn with Boris? He

I have already explained this in the context of Gmail, but I thought we should make it more explicit. If you go on Music Oricon Japanese Web site with Firefox Android with about:config?filter=prefixes.webkit set to false, you will see massive breakages, including this navigation bar: There are a couple issues including flexbox, but let's ignore it for the moment and let's focus on background-image

Lun 01 février 2016 by Karl Dubost (Worked at Mozilla from 2013 to 2022) Google is serving very different versions of its services to individual browsers and devices. A bit more than one year ago, I had listed some of the bugs (btw, I need to go through this list again), Firefox was facing when accessing Google properties. Sometimes, we were not served the tier 1 experience that Chrome was receivi

Lun 04 janvier 2016 by Karl Dubost (Worked at Mozilla from 2013 to 2022) I mentioned it in my worklog last week. On 2016-01-02 09:39:38 Japan Standard Time, Mozilla closed a very important issue enabling a new feature in Firefox: Bug 1213126 - Enable layout.css.prefixes.webkit by default . Thanks to many people for this useful work. First, because an image is sometimes worth 1000 words, let's look

Sam 19 décembre 2015 by Karl Dubost (Worked at Mozilla from 2013 to 2022) Week-end travel Coming back from a work week in Orlando. I woke up on Friday morning (3am Orlando) to arrive at home on Sunday evening around (6pm Japan). I decided to take Monday off for getting a bit of slip and straight up things. Discussions started to how to organize the work on contacting the developers of e10s + addon

Mar 03 novembre 2015 by Karl Dubost (Worked at Mozilla from 2013 to 2022) During the last TPAC meetings (October 2015, Sapporo), Google convened during the unconference about AMP (Accelerated Mobile Pages), their new project. Jeremy Keith has a very good blog post about it. Rather than creating a proprietary format from scratch, it mandates a subset of HTML …with some proprietary elements thrown i

Working on Web Compatibility issues for Japan is a kind of nightmare. The two biggest offenders are first versions of WebKit flexbox and gradient. Basically Web developers hurried to use flexbox for their Web sites, but never dared fixing it when the new stable syntax had been released. Web Developers used CSS prefixes to support browsers Browsers have to support Web sites because of their outdate

I'm living in Japan. And time to time, I'm confronted with issues on the Japanese market when using Firefox on Mobile (Firefox OS and Firefox for Android). There's a situation in Japan which has similarities with the Chinese Market. For example, many sites have been designed with old WebKit CSS properties only, such as flexbox. The sites have not been updated to the new set of properties. We start