Some news
-
What happens when/if iOS authorizes other rendering engines?
-
I have been working 8 years at Mozilla in Webcompat. What a team!
-
I would love to have a better bookmarks and tabs management. This morning a simple sketch on what it would look like.
-
In 2022, Firefox and Chrome will reach a version number with three digits: 100. It's time to test. Help us!
-
Let's keep the possibility of hackability when simplifying interfaces
-
These are my requirements and tips when working in a remote distributed team at Mozilla.
-
Capping User Agent string for Web Compatibility, a meeting and a status, and probably future work on evolving freezing user agent strings.
-
Code Review is an essential part of the process of publishing code. We often talk about the benefits of code review for projects and for people writing the code. I want to talk about the benefits for the person actually reviewing the code.
-
MacOS 11 and a story of breakage.
-
I often want to bookmark a part of a text more than a page.
-
When serious topics need to be addressed seriously.
-
We need to improve site interventions, probably using webdriver and starts with a very simple solution, so everyone can be involved.
-
What do you understand when you hear career opportunities?
-
video html element has improved usability a lot, but this is a baby step. We should deserve better.
-
Slowing down to understand better.
-
Starting a new era of webcompat team
-
Khmer line breaking is not implemented (yet) on Firefox Android.
-
Let's talk about distressful content filtering on the Web
-
Some dates around developer tools
-
Spending a lot of times in devtools and wanted to work better. Today Formatted console.log lines and stack traces.
-
Working differently, not converting.
-
Let's talk about contextual reading in a tab
-
Let's talk about tabs management and their content as a space for exploration.
-
Short recommendation for blogging for Mozilla engineers.
-
from work to human core dump.
-
First part of the week was about unbreaking things. Computers are sometimes just a mess.
-
everything is falling apart
-
Starting to dive into Machine Learning with python and as always a bit of diagnosis.
-
fixed issues with flask blueprint and pytest is now working
-
Anonymous reporting is on! Also explaining name conflicts in python flask blueprint when testing
-
Finishing coding the anonymous workflow reporting. Jetlag. And virus monitoring.
-
Mozilla Berlin All Hands - January 2020 - day by day
-
python coding all day long.
-
Coding, coding, coding the new anonymous workflow
-
This week will be not fun, but interesting.
-
We need to think again how we handle the webcompat anonymous reporting, but for now an overview of the current context.
-
The (work) week started on January 2 for me. So that will cover only 2 days.
-
This is the last week of 2019 for me. Holidays and battery recharging at the corner.
-
A mix of diagnosis and webcompat outreach. Trying to recover from last week.
-
Attacked by a bug, a cold, a cactus in the throat and more webcompat issues.
-
Some notes and thoughts taken at the JSConf JP 2019.
-
Opus 2 of the week notes, let's see where it goes.
-
CSS zoom, a non-standard property creating web compatibility nightmares for Mozilla
-
Some week notes, let's see where this is going. A record of my work week.
-
We want to separate the images saving infrastructure from the rest of the webcompat.com service.
-
Some notes about the webcompat talk for Mozilla Dev Roadshow 2019 and a couple of other things noticed along the way.
-
Remote working is a kind of fallacy. Let's unpack some of the things around it.
-
In the process of moving webcompat.com to python 3, I tried to learn a bit more about Docker and containers. These are just simple notes and references.
-
Some quick notes without a specific order about my impressions during the Mozilla All Hands 2019 in Whistler.
-
Big platforms start to be interested by privacy, because it's a new marketing word, which can give them profits.
-
A summary of the cool things done by Mozilla Core Engineers for webcompat. Second Edition
-
A summary of the cool things done by Mozilla Core Engineers for webcompat. This is the first edition.
-
Edit a JavaScript file on the fly to be able to debug a site is now possible.
-
On July 2, 2013, I was hired by Mozilla on the Web Compatibility team. It has been 5 years.
-
Life in a golden jail.
-
Bigger roads rarely solves the issues of traffic jam, nor faster browsers solve the issue of web cluttering.
-
A simple question difficult to answer about Netscape source code.
-
Default fonts on Android is not a safe bet. We share a technique to minimize the Web compatibility issues with Clear Sans and Roboto.
-
The SVG icons in unstyled pages are big. You can fix this.
-
How to make sure you are reporting a real Web Compatibility issue? How to organize an effective webcompat sprint event?
-
What's wrong with work gamification?
-
Publishing code benchmarks is often used as a way to show the world how a product outperformed the competition. This is most of the time meaningless.
-
some bugs
-
Some random notes on things I type when working on webcompat.com development.
-
Walking in the streets and meeting with my thoughts.
-
some bugs
-
A strange week, with a big chunk of interesting work and sometimes a bit on the edge.
-
A busy week with still a flood of type-media issues and the fatigue after Berlin's work week.
-
some bugs, some life
-
The spring is coming back and it feels good.
-
In my summary, I tend to put only the interesting issues. This week a bit of ellipsis, strange tables and flexbox.
-
Most of the Web compat bugs are twisted and threaded into history.
-
Another useless stone in the debate about CSS. I'm not trying to solve anything in here.
-
How to print messages even when the tests are successful.
-
httpie was failing with a SSLv3 Handshake failure.
-
Went to Normandy, working from there.
-
It is raining. Viewport and client-hints. A lot of development on Webcompat.com
-
Sharing what you are working on is good for you, but it is also good for the rest of your distributed team.
-
Bugs take time. Sometimes so long that they disappear.
-
Exploring WebKit C++ code and other web compatibility bugs.
-
Everything takes time and the end result is not necessary what we were fearing.
-
Discussions on webcompat.com dev have accelerated.
-
Many issues have been opened in the last couple of weeks around webcompat.com project. We need to make it better, but we need also need to implement things. Time to code.
-
Is it possible to travel for a work week without any data on your laptop?
-
We got a new button that brings a new series of issues for our work process.
-
Too many choices, not enough choices, UI for getting the user feedback is always hard.
-
A lot of discussion about webcompat.com for this 51th worklog.
-
Trying to better understand my own work policy when discussing with others.
-
Spent a lot of times, exploring why Selenium 3.0 was not working with our functional tests. It probably was not Selenium but intern.
-
Let's do that again
-
End of the year 2016. 2017 is full of mistery or misery?
-
Simple summary of the Christmas time worklog.
-
A work week in Hawaii
-
The text version of the talk given at Tech in Asia Jakarta 2016 on November 16, 2016 at the Developer stage.
-
Worklog : Edition 044
-
Worklog : Edition 044
-
Worklog : Edition 043
-
Worklog : Edition 042. The after effects of work week is always good. No matter how tiring was the work week.
-
Worklog : Edition 041. Web compat team work week.
-
Worklog : Edition 040. When everything is source of difficulties.
-
Worklog : Edition 039. The usual list of bugs and work on Web compatibility.
-
A very quick and simple tip to understand the CSS boxes in a document when debugging.
-
Worklog : Edition 038. Converting to Python 3 is less hard than I thought initially.
-
Worklog : Edition 037. Short work week but important.
-
Worklog : Edition 036 - A lot of non direct Web Compatibility work.
-
We type code so we do mistakes.
-
Worklog : Edition 035. PNG can be invalid and other bugs.
-
Testing different viewport options on mobile
-
Worklog : Edition 034. Sometimes you just need to clean up the bottom of this drawer where bugs have accumulated and gathered dust.
-
Forms are a strange thing on the Web that developpers are breaking in many ways. This time, display: none for making the instruction non selectable.
-
Worklog : Edition 033. The season of typhoons started. Time to do bugs clean-up
-
Worklog : Edition 032. So many bad issues.
-
Worklog : Edition 031. Some interesting new issues about mask, remoteEventListener, etc.
-
Worklog : Edition 030. Another week of work from the 7th floor with the prize of a beautiful rainbow.
-
Worklog : Edition 029. Rinse and Repeat is what we do.
-
Worklog : Edition 028. A bit of prefixes, a bit of Google issues and some work on appearance.
-
Worklog : Edition 027. tracking protection, CSS issues, and boxes.
-
Worklog : Edition 026. Summer in Japan.
-
Worklog : Mozilla worked all the week in London.
-
Worklog : Edition 025. legend and border-image are not good friends. Left to implementations is not a good idea.
-
Finally an answer to my question about AMP.
-
Should you block users because your site is not perfect or should you let them fail?
-
When we talk about Progressive Web Apps, we are mainly talking about user experience for the Web. There's one I would love to see: the silo.
-
Worklog : Edition 024. Too much spam. Fixed redirection and very too long trip.
-
Progressive Web Apps were the drama of these last couple of days.
-
Worklog : Edition 023. Understanding Gecko code to better understand Webcompat bugs.
-
CSS widths in Gecko are not stored and computed the same way than you would imagine. Follow up on yesterday's blog post.
-
When it comes to CSS width using percentage can be dangerous.
-
border-image syntax has evolved a bit and it needs a couple of fixes.
-
When you say remoter workers, you already failed your intents of having an effective team.
-
Worklog : Edition 022. Testing libraries and understanding their impacts.
-
Worklog : Edition 021. It's basically harder to make a solid simple Web site. But that the cost is beneficial on the longterm.
-
The endless debate about what is a Web standard.
-
Worklog : Edition 020. Golden Week. Less work, busy with life.
-
Worklog : Edition 019. Google is fixing stuff for Firefox. There's certainly a good change of policy.
-
Worklog : Edition 018. Let's shake the Web.
-
Checking the state of art in the summary details proposal
-
Worklog : Edition 017. Some bugs, a lot of fatigue, but the spring is really here.
-
Documenting shortly the way I work on webcompat.com
-
Worklog : Edition 016. It takes time to get things fixed. But it's worth the wait.
-
When choosing a platform to publish your information, be very careful to understand the consequences on content distribution.
-
Worklog : Edition 015. Security, organizing the trip to London and other small things.
-
Worklog : Edition 014. A couple of bugs tainted by a mad world.
-
Worklog : Edition 013. Nice work week with a lot of thinking on how to make a better community around Webcompat. Also a lot of code review for the new contributors.
-
With HTTP, too many servers have lost their HEAD and it's quite sad to see that.
-
a couple of key strokes to fix gmail and makes it a near perfect experience for users.
-
Nothing better than a sudden surge of contributors for challenging your assumptions about your project environment and in the end your own ways of working.
-
Worklog : Edition 012. Infinite redirection, stacked labels, …
-
Worklog : Edition 011. Being able to restart a bit more seriously Web development for webcompat.com and a couple of bugs
-
Worklog : Edition 010. Writing about CSS properties and their implementations and some funny bugs.
-
border-imageis not interpreted the same way in Chrome and Firefox. Let's see what we can do. -
Defining appearance button in a form might have unfortunate renderings when combined with CSS vendor prefixes.
-
Worklog : Edition 009 A lot of reading and a lot of bugs closing.
-
Worklog : Edition 008 Some funny bugs and restarting slowly the development of webcompat.com
-
Worklog : Where I keep notes of things I have been working on during the week - Edition 007. This week I went through ~600 old bugs and a few other things.
-
Sometimes another team of Mozilla will ask help from Webcompat team for contacting site owners to fix an issue on their Web site which hinders the user experience on Firefox. Let's go through some tips to maximize the chances of getting results when we outreach.
-
Google is used to send very tailored HTTP responses for some of his properties to devices. I tested again Google Search on Gecko.
-
Worklog : Where I keep notes of things I have been working on during the week. APZ bugs, Some webcompat bugs and HTTP Refresh
-
Worklog : very short worklog, trying to get over the backlog.
-
A short summary of one year of work on helping users to have a better experience on the Web
-
Worklog - No plans, no resolutions
-
Worklog - some notes about the week of work. Starting the work on addons.
-
Worklog - some notes about the week of work.
-
A demo illustrating a travel made with SVG, canvas and HTML which is still readable when JS and CSS are cut.
-
Some notes after a work week in the land of Disney.
-
What is the best way to organize the CSS for a better compression rate?
-
What should come first? Content or UI when designing Web sites which are acting like apps.
-
AMP is a new proposed format by Google. What and Why?
-
Quick thought about interface mockups
-
You can now show the issue when you are reporting an issue on webcompat.com
-
People like dichotomies and they will do everything to have their story fits the imaginary gap.
-
Daniel Glazman gives us a bit of history and context about CSS Vendor Prefixes.
-
While the vendor prefixes are a good idea on paper, they translate into the market in uncalled realities that hinder both the progress of the Web and cost to Web developers.
-
The Web Components battle has the smell of an old modularity battlefield: CDF.
-
Many people have a really hard time to understand what a computing engineer does and why it takes so much time, here an answer.
-
Emails are not a bad way of working if everyone is using them correctly.
-
Because I want to minimize my hassles, I have started a project configuration for mozilla-central in SublimeText.
-
After finding a difference of behaviors in between browsers, I went on a journey of modifying Firefox through a patch.
-
The damage of keeping old CSS syntax without the new standardized properties.
-
A reddit question about Web compatibility asking what are the essentials to know.
-
How do you convince people that they really need to fix their Web site.
-
Solving Web Compatibility issues require to contact people. How do you find the right contact information when you have no personal connection with the site.
-
Some findings and possible actions for Web Compatibility in Japan
-
On documenting outdated and deprecated features but still implemented.
-
Reviewing specification is definitely a good way to learn about technologies and understand them in a more global way.
-
Bugs get quickly old and forgotten. Knowing when and how to attract a renewed focus on them is difficult. Let's explore some ideas.
-
A summary of the Web Compatibility Summit we held in Mountain View on February 18, 2015.
-
Newly hired introductions to the rest of Mozilla do not have to be boring.
-
We often forgot that working openly is not something that many people understand or are used to.
-
When developing a Web site, we rely on plenty of scripts and libraries. These are becoming too quickly legacy.
-
max-width CSS property seems to be an easy win for fluid design, but it creates Web compatibility issues in some circumstances.
-
Mostly in Asia, many Web sites are designed using -webkit- CSS web properties. Sometimes the fix is really easy. Here the case of hao123.com.
-
Testing Web compatibility issues requires to have the most neutral environment possible. We are explaining how to configure Firefox on a clean profile.
-
Web agencies develop skills and abilities around a core set of values and often miss the boat for other parts.
-
Web Compatibility bugs are touching many sites across the world. Google services create issues with Firefox and other browsers, here's a list.
-
Learn how to remove the UA override from Firefox OS.
-
Monitoring web pages changes more or less automatically is a challenge. There are different techniques. Would it be possible to use screenshots?
-
Browsers have a ton of legacy in their UI and UX due to the first time, they have been built. How can we improve them?
-
IE has implemented some aliases for WebKit properties. What does it mean?
-
Why would we waste bandwidth for automatic browser requests? Here some quick tips on how to configure your server to save a bit of bandwidth.
-
An issue with mediaqueries syntax which is failing everywhere but Safari.
-
Counting Mentor Bugs With Python
-
Very simple step by step way of finding bugs in Bugzilla.
-
The battle over UA simplification is on many fronts.
-
Each local market has patterns of bad practices. Here in China, we noticed quite a number of sites sending Firefox OS WAP content.
-
How do you test for Web Compatibility across browsers and Web sites? Discover sitecomptester-extension.
-
User Agent detection is a delicate technique with many pitfalls. What is it? Why do people need it? Do we need to rethink it?
-
Trip repory about Web Chinese Market and Web Compatibility issues as of March 2014.
-
The implementation of HTTP verbs is sometimes surprising. It makes the testing harder.
-
How adding a few CSS flexbox new syntax properties fix things quickly.
-
When old is old when we consider browsers?
-
A list of comments and links about Web Compatibility
-
So what do you mean when you say future fail?
-
When typing text in forms there are cases where it is practical to have autocomplete and spelling from the browser and sometimes when it's not. Let's go through it.
-
We created Web compatibility planet, time to uglify the Web.
-
When hardcoded string is bad, even for UA detection.
-
Here a classical example on the many ways the User-Agent detection is not living by its promises.
-
You started a new product, a new browser and you realize that it is failing on some Web sites at a large scale. You want to fix this. Here a few ideas on how to start your own Web compatibility activity.
-
When a browser is making a request to a server, it has sometimes to not tell the full truth about its identity
-
Sometimes, servers have a certain poetry with regards to data they receive. UA detection is always a maze of surprises.
-
HTTP gives everything you need for redirections
-
Some UA strings have a device ID. Is it an issue to have it or to not have it?
-
Parsing a UA string is an art, but not for regex.
-
Compatibility to what? UA detection has created an ecosystem.
-
When mediaqueries get into the way, and make your Web site unusable.
-
User Agent sniffing, an old pain
-
The User Agent detection algorithm leads to horrors in terms of detection. My policy has always been « just don't do it. » Sometimes diving into a JavaScript helps understand what is happening.
-
To have an idea of what's going on very quickly for a list of domain names, I often use combinations of pipes, httpie, sed, awk, xargs and grep.
-
Understanding HTTP transactions is key to good Web development. Firefox 23 introduces the Network Panel in the Web developer tools.
-
UA (User Agent) sniffing has some patterns. We can define some "rules" related to that. Let's fight!
-
For analyzing HTTP transactions, httpie is a very good lightweight tool. It is easy to install and use. There are a few things I use on a regular basis worth sharing.
-
An attempt explaining this blog.
-
And if we were implementing HTTP from scratch? What would be the sequence of interactions?
-
An automatic redirection with an unknown scheme.
-
_