Being born in France, lived/ing in Canada and Japan, The international news pages are usually my preferred source of information about the world. But when I read the non-comical farce and quite disheartening run for the USA presidential 2016, I'm dumbfounded. Quick, poetry and imagination! Tune of the week: Ol' Man River - William Warfield
Webcompat Life
Progress this week:
Today: 2016-10-11T07:15:20.170216
363 open issues
----------------------
needsinfo 19
needsdiagnosis 123
needscontact 12
contactready 20
sitewait 170
----------------------
You are welcome to participate
I'll be speaking in Jakarta, Indonesia for Tech in Asia 2016 on November 16.
Preparing a brownbag for Taipei's office.
Webcompat issues
(a selection of some of the bugs worked on this week).
- padding and letter-spacing breaks the menu
- ::-webkit-scrollbar is a thing which seems to be used a lot.
- A ninja shopping cart
- NYTimes in an infinite loop state of Mind. Cue Alicia Keys.
Webcompat.com development
- Creating thumbnails for uploaded images to solve issue 722. I have fun when I code in python.
Reading List
-
will-changeused too often. The thing I found interesting in this article is that it is written entirely from the prospective of Chrome without any tests in other browsers. This is one of the issues of the way some people think about the Web. Firefox is sending a warning in the console when people over-usewill-change. fwiw the code provided in the article works very well in Firefox/Gecko and Safari/WebKit (testing in Edge would be cool too) and indeed shows bluriness in Blink (Opera and Chrome).The will-change spec doesn't really specify implementation details which means that Chrome's new behavior may be completely unique; Firefox might do something different, and then there's Edge, Safari, Opera, Android, etc. Perhaps Chrome requires that developers toggle back-and-forth to maintain clarity, but what if Firefox interprets that differently, or imposes a big performance penalty when doing the same thing? What if developers must resort to various [potentially conflicting] hacks for each browser, bloating their code and causing all sorts of headaches. We may have to resort to user agent sniffing again (did you just throw up a little in your mouth?). This will-change property that was intended to SOLVE problems for animators may end up doing the opposite.
Follow Your Nose
TODO
- Document how to write tests on webcompat.com using test fixtures.
- ToWrite: Amazon prefetching resources with
<object>for Firefox only.
Otsukare!