planet.webcompat.com

otsukare by Karl Dubost at

Last week, the Web compat team met in Taipei to work together on webcompat.com and gofaster add-on. This week, the work has a more special human feeling. Work week meetings are good for creating a better sense of community. Tune of the week: Empire State of Minds

Webcompat Life

Progress this week:

Today: 2016-10-31T07:47:33.647004
341 open issues
----------------------
needsinfo       17
needsdiagnosis  71
needscontact    2
contactready    30
sitewait        181
----------------------

You are welcome to participate

Webcompat issues

(a selection of some of the bugs worked on this week).

Reading List

I often joke that I don’t want to hire a code ninja. Ninjas come in the middle of the night and leave a bloody mess. I want a code janitor. Someone who walks the hallways of code, cleaning up pieces, dusting up neglected parts, shinning up others, tossing unnecessary bits. I prefer this gentler, more accurate analogy. This is the person you want on your team. This is a person you want in your code reviews. On Style Maintenance

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!

otsukare by Karl Dubost at

This is a very short summary of a couple of things we did during the work week. There is more to come in the following weeks.

  • Done triage on webcompat.com and refocus on some of the milestones.
  • Hacking on some of the issues for webcompat.com
  • Collaborative debugging
    • Dennis, Adam: qemu-system emulator
    • Adam: VPN for international testing
    • We showed our different ways of debugging and process.
    • Debugging process can take a lot of time.
    • jsnice.org very useful for deminifying
  • We need to investigate viewport in Firefox and different browsers. Good stuff here. I will do it.
  • Site Patching Policy
  • Triage First steps (discussion with Adam). How do we empower the community? How do we do ourselves. Our criteria for advancing an issue to the next stage.
  • Planning Q4 and Topics list for H1 2017
    • Time for us to commit on things we need to achieve before the end of the year and things we want to move on in 2017.
  • Ligthning Talk
    • Mike explains webcompat
    • Karl talked about why is hard to get a Web site fixed. Social, economic and technical dynamics.
    • Dennis talked about MITM for hot testing a Web site.
    • Adam talked about Screenshot diffing https://github.com/yahoo/blink-diff
    • Eric talked about the situation of Web compat in China and Taiwan.

Otsukare!

otsukare by Karl Dubost at

Family with cold, just before the work week. Rain. Administrative Chores .On and on. Tune of the week: Erika Badu - On and on

Webcompat Life

You are welcome to participate Monday was a day off in Japan: Sports day

Webcompat issues

(a selection of some of the bugs worked on this week).

Webcompat.com development

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!

When Can I Use updates by Alexis Deveria at

In addition to the existing "current aligned" & "usage relative" modes, caniuse now has a "date relative" mode for support data.

This mode, toggled via the button above the support table, organizes the support data relative to when each browser version was released. As a result, you can get an idea how support for a feature changed over time.

The tooltip information seen when hovering over versions now also includes the browser's release date, which appears in all three visualization modes.

otsukare by Karl Dubost at

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).

Webcompat.com development

Reading List

  • will-change used 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-use will-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!

otsukare by Karl Dubost at

Reading The GDS blog post on how to prototype in the browser, I realized that it's always good to explain little tips for the benefits of others. Their technique is something I use on a daily basis for modifying content, evolving a design, etc.

When diagnosing on webcompat.com, I often use a trick for having a better understanding of the way the elements flow with regards to each other.

Using CSS outline for visualizing

David Lorente reported an issue about the menu of Universia. Basically two items where missing in the main navigation bar of the Web site.

Hovering the menu with the mouse and doing ctrl+click to get the contextual menu, I can choose inspect.

Inspect Contextual Menu

It opens the developer tools and place the cursor on the right element and displays its associated CSS.

Inspector

For this particular issue because the elements were not immediately visible. I decided to add a higher z-index in case there were hidden by another layer, but more specifically. I selected the wrapper element for the navigation bar <div class="header-nav"> and headed to the + sign on the right side.

Add new rule

Clicking on it will help you to add a new rule for this selected node (element) in the inspector. In this case, it will add .header-nav.

header nav selector

which I usually edit for adding all the children of this node with .header-nav *. Then I proceed to add an outline CSS property with a color which will give an acceptable contrast, helping me to understand what is happening. In this case outline: 1px solid pink

outline css rule

The result helps to visualize all the children boxes of the div.

Visualization

It is now a lot easier to understand what is going on.

Why CSS outline?

The reason I use CSS outline is that they do not participate to the intrinsic sizes of boxes and does not destroy the flow of boxes. It just makes them visible for the purpose of the diagnosis.

What are the tricks you are using which seems obvious to you? Share them with others.

Oh and the site has been fixed since.

Otsukare!

otsukare by Karl Dubost at

I managed to break a bit of my python installation. I will need to figure out next week. Taipei is coming quickly, then seems I will be speaking at another event in November. Tune of the Week: Jardin d'hiver

Webcompat Life

Progress this week:

Today: 2016-10-03T11:13:33.042445
347 open issues
----------------------
needsinfo       14
needsdiagnosis  109
needscontact    12
contactready    23
sitewait        166
----------------------

You are welcome to participate

Webcompat issues

(a selection of some of the bugs worked on this week).

Webcompat.com development

Reading List

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!

otsukare by Karl Dubost at

Two Japanese national holidays during the week. And there goes the week. Tune of the Week: Anderson .Paak - Silicon Valley

Webcompat Life

Progress this week:

Today: 2016-09-26T09:24:48.064519
336 open issues
----------------------
needsinfo       13
needsdiagnosis  110
needscontact    9
contactready    27
sitewait        161
----------------------

You are welcome to participate

  • Monday day off in Japan: Respect for the elders.
  • Thursday day off in Japan: Autumn Equinox.

Firefox 49 has been released and an important piece of cake is delivered now to every users. You can get some context on why some (not all) -webkit- landed on Gecko and the impact on Web standards.

We have a team meeting soon in Taipei.

The W3C was meeting this week in Lisbon. Specifically about testing.

I did a bit of Prefetch links testing and how they appear in devtools.

Webcompat issues

(a selection of some of the bugs worked on this week).

  • Little by little we are accumulating our issues list about CSS zoom. Firefox is the only one to not support the non-standard property. It's coming from (Trident) IE was imported in WebKit (Safari), then maintained alive in Blink (Chrome, Opera) to finally come into Edge. Sadness.

Webcompat.com development

Reading List

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!

otsukare by Karl Dubost at

Busy week without much things done for bugs. W3C is heading to Lisbon for the TPAC, so tune of the week: Amalia Rodrigues. I'll be there in spirit.

Webcompat Life

Progress this week:

326 open issues
----------------------
needsinfo       12
needsdiagnosis  106
needscontact    8
contactready    28
sitewait        158
----------------------

You are welcome to participate

Webcompat issues

(a selection of some of the bugs worked on this week).

  • yet another appearance: none implemented in Blink. This time for meter.

Webcompat.com development

Reading List

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!

otsukare by Karl Dubost at

Because we type code. We do mistakes. Today by chance my fingers typed viewpoet instead of viewport. It made me smile right away and I had to find out if I was the only one who did that typo but in actual code. So I started to search for broken code.

  • viewpoet

    Example: <meta name="viewpoet" content="width=devide-width">

  • transitoin

    Example: this.$element.on("transitoinEnd webkitTransitionEnd", function() {

  • gradeint

    Example: background: linear-gradeint($direction, $color-stops);

  • devixe

    Example: <meta name="viewport" content="width=devixe-width, initial-scale=1.0">

Slip of mind, dyslexia, keys close to each other, many reasons to do beautiful typos. As Descartes was saying:

I do typos therefore I am.

Otsukare!

otsukare by Karl Dubost at

Discovering a new thing to eat on a local market and Tune of the week: Pastoral Symphony - Beethoven

Webcompat Life

Progress this week:

314 open issues
----------------------
needsinfo       10
needsdiagnosis  98
needscontact    19
contactready    31
sitewait        149
----------------------

You are welcome to participate

Webcompat issues

(a selection of some of the bugs worked on this week).

  • When your design is only working in Blink and probably not because the developer meant to make it work for Blink, but probably because it was only tested with this rendering engine.
  • A problem with PNG, not being sure of the origin of the issue, I opened a bug on Core/ImageLib. The PNG file is working in WebKit and Blink, not in Gecko.
  • When a Gecko/Firefox rendering issue is in fact a Blink/Chrome bug, probably inherited from Webkit/Safari. This is a symptom of a pattern where one rendering engine is trusted and not checked against specs and other browsers.
  • Going through a lot of the yahoo.co.jp Web sites, around 100 of them to assess the ones which are working and those who are failing. I should probably something about it.

Webcompat.com development

Reading List

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!

Mike Taylor's Web Log by Mike Taylor at

It's almost Septemberween, which means it's that time of the year we gather 'round our spinning MacBook fans and share website ghost stories:

The tale of the disappearing burger and lobster site content (i.e., webcompat bug 2760).

Chapter 1.

Once upon a time (that time being the present), there was this burger and lobster "restaurant" called, um well, burger and lobster. In Firefox, as of today, the site content never renders — you just end up with some fancy illustrations (none of which are burgers or lobsters).

Opening devtools, you've got the following mysterious stacktrace:

Error: node is undefined
compositeLinkFn@http://www.burgerandlobster.../angular-1.2.25.js:6108:13
compositeLinkFn@http://www.burgerandlobster.../angular-1.2.25.js:6108:13
nodeLinkFn@http://www.burgerandlobster.../angular-1.2.25.js:6705:24
(...stack frames descend into hell...)
jQuery@http://www.burgerandlobster.../jquery-1.11.1.js:73:10
@http://www.burgerandlobster.../jquery-1.11.1.js:3557:1
@http://www.burgerandlobster.../jquery-1.11.1.js:34:3
@http://www.burgerandlobster.../jquery-1.11.1.js:15:2

Cool, time to debug AngularJS.

But it turns out that leads nowhere besides the abyss, AKA funtions that return functions that compose with other functions with dollar signs in them... and the bug is elsewhere. Besides, Chrome has a similar error, and the page works there. Just a haunted node, maybe.

Dennis Schubert discovered that adding a <base href="/"> fixes the site, which happens to be required by Angular is later versions for $locationProvider.html5Mode. But this bug has nothing to do with pushState or history, or even SVG xlink:hrefs, all of which the <base> element can affect.

Another (dead) rabbit hole, another dead end (spooky).

At some point, all your debugging tricks and intuitions fail and it's time to just page a thousand lines of framework-specific JS into your brain and see where that leads. Two hours later, if you're lucky, you notice something weird like so:

var illustArr = [
  {
    "url": "/Assets/images/illustrations/alert-man.png",
    "x": "2508",
    "y": "2028"
  },
...
(bunch of similar objects objects, then...)
  {
    "url": "",
    "x": "",
    "y": ""
  };

And you recall a method that dispatches a allImagesLoaded event which tells the app it's OK to load the rest of the page content. It looks like this:

b.allImagesLoaded = function() {
  d += 1,
  d === a.imageArr.length && $("body").trigger("allImagesLoaded")
}

But it only does that once it's counted that all images have loaded (or fired an error event):

l.loadImage = function(a) {
  var b = $(document.createElement("div"))
    , c = $(document.createElement("img"));
  [...]
  c.attr("src", a.url),
  [...]
  c.bind("load error", function(e) {
      $(this).addClass("illustration--show"),
      h.allImagesLoaded()
  })
}

So yeah, that looks fishy. And that's why Firefox gets stuck—it doesn't fire error events when img.src is set to the empty string, which is required per HTML. Here's a small test case, which also demonstrates why the <base href="/"> fixed the page—it'll fire an error event when requesting an image from the site root (and eventually barf on the HTML, I guess).

Anyways, the Gecko bug for that is Bug 599975. That will probably get fixed soon.

Epilogue.

So what's the moral of this ghost story? There is none. Septemberween is cruel that way.

otsukare by Karl Dubost at

Viewport

We had a couple of Web Compatibility issues on the rendering of some sites related to the viewport information. Here after is a preliminary test for trying to figure out what are the sources of variability.

The major visible difference is only for the last case where Firefox and Chrome do something different.

I haven't tested all combinations yet. Just a couple to have an idea. This is preliminary work to figure out the Web Compatibility space.

Maybe I can adjust tests in the future.

case A and case F below seems to highlight differences in between Gecko and Blink. Chrome seems to apply different logic for resizing the content.

Device parameters for the test

Using this page instrospection tool

Safari 9.0 OS 9.3.5

window.innerWidth = 320
window.outerWidth = 0
window.screen.width = 320
document.documentElement.clientWidth = 320
window.devicePixelRatio = 2

Firefox Nightly 51

window.innerWidth = 360
window.outerWidth = 360
window.screen.width = 360
document.documentElement.clientWidth = 360
window.devicePixelRatio = 3

Chrome/Opera 52

window.innerWidth = 360
window.outerWidth = 360
window.screen.width = 360
document.documentElement.clientWidth = 360
window.devicePixelRatio = 3

Results for different viewport content adaptation

  1. width=250 with 700px paragraph
  2. width=250 with free width paragraph
  3. width=450 with 700px paragraph
  4. width=450 with free width paragraph
  5. common no scalable viewport with 700px paragraph
  6. scalable viewport with 700px paragraph

Case A. width=250px with larger paragraph

Screenshot of chrome viewport

Screenshot of firefox viewport

Screenshot of safari viewport

Case B. width=250px with no paragraph size

Screenshot of chrome viewport

Screenshot of firefox viewport

Screenshot of safari viewport

Case C. width=550px with larger paragraph

Screenshot of chrome viewport

Screenshot of firefox viewport

Screenshot of safari viewport

Case D. width=450px with no paragraph size

Screenshot of chrome viewport

Screenshot of firefox viewport

Screenshot of safari viewport

Case E. not scalable with larger paragraph

Screenshot of chrome viewport

Screenshot of firefox viewport

Screenshot of safari viewport

Case F. scalable with larger paragraph

Screenshot of chrome viewport

Screenshot of firefox viewport

Screenshot of safari viewport

Otsukare!

otsukare by Karl Dubost at

Sometimes you just need to clean up the bottom of this drawer where bugs have accumulated and gathered dust. But by the end of it, it brings light to your work and process. Tune of the week: Jamiroquai - Cosmic Girl

Webcompat Life

Progress this week:

Today: 2016-09-05T08:10:37.674672
312 open issues
----------------------
needsinfo       9
needsdiagnosis  93
needscontact    17
contactready    31
sitewait        148
----------------------

You are welcome to participate

Webcompat issues

(a selection of some of the bugs worked on this week).

  • Still going through the list of old bugs. So most of this week has been bug triage and contacting.

Reading List

  • Review of input type='number' and its implementations.
  • ❤️ Memento: "Adding Memento support to versioning systems allows a client to uniformly access the version of a resource that was active at a certain moment in time (TimeGate) and to obtain its version history (TimeMap). When a version page in a system that supports Memento links to a resource that resides in another system that supports Memento, a client can uniformly access the version of the linked resource that was active at the same moment in time. "

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!

otsukare by Karl Dubost at

Let's develop a bit more on an issue that we have identified last week.

On the croma Web site, they have a fairly common form.

Croma Store Form

As you can notice the instruction "Select City" for selecting an item is in the form itself. And the markup of the form looks like this.

<div class="ib">
    <!-- Customization start here for store locator -->
    <div id="citydropdown" name="citydropdown" class="inpBox">
        <select id="city" name="city" onchange="drop_down_list1()">

            <option value="" style="display: none">Select City</option>

            <option value="AHMEDABAD">AHMEDABAD</option>
            <option value="AURANGABAD">AURANGABAD</option>
            <option value="BANGALORE">BANGALORE</option>
            <option value="CHANDIGARH">CHANDIGARH</option>
            <option value="CHENNAI">CHENNAI</option>
            <option value="FARIDABAD">FARIDABAD</option>
            <option value="GHAZIABAD">GHAZIABAD</option>
            <option value="GREATER NOIDA">GREATER NOIDA</option>
            <option value="GURGAON">GURGAON</option>
            <option value="HYDERABAD">HYDERABAD</option>
            <option value="MUMBAI">MUMBAI</option>
            <option value="NASIK">NASIK</option>
            <option value="NEW DELHI">NEW DELHI</option>
            <option value="NOIDA">NOIDA</option>
            <option value="PUNE">PUNE</option>
            <option value="RAJKOT">RAJKOT</option>
            <option value="SURAT">SURAT</option>
            <option value="VADODARA">VADODARA</option>
        </select>
    </div>
</div>

Basically the developers are trying to make the "Select City" instruction non selectable. It works in Safari (WebKit) and Opera/Chrome (Blink) with slight differences. I put up a reduced test case if you want to play with it.

The bug with display: none

It fails in Firefox (Gecko) in an unexpected way and only for e10s windows. The full list of options is not being displayed once the first one is set to display: none

Test results on Firefox

Do not do this!

If you really want the instruction to be part of the form, choose to do

<div class="ib">
    <!-- Customization start here for store locator -->
    <div id="citydropdown" name="citydropdown" class="inpBox">
        <select id="city" name="city" onchange="drop_down_list1()">

            <option value="" hidden selected disabled>Select City</option>

            <option value="AHMEDABAD">AHMEDABAD</option>
            <option value="AURANGABAD">AURANGABAD</option>
            <!-- cut for brevity -->
        </select>
    </div>
</div>

This will have the intended effect and will "work everywhere". It is still not the best way to do it, but at least it is kind of working except in some cases for accessibility reasons (I added the proper way below).

That said, it should not fail in Gecko. I opened a bug on Mozilla Bugzilla and Neil Deakin already picked it up with a patch.

Quite cool! This will probably be uplifted to Firefox 49 and 50.

select menu form, the proper way

There are a couple of issues with regards to accessibility and the proper way to create a form. This following would be better:

<div class="ib">
    <div id="citydropdown" name="citydropdown" class="inpBox">
        <label for="city">Select City</label>
        <select id="city" name="city" onchange="drop_down_list1()">
            <option value="AHMEDABAD">AHMEDABAD</option>
            <option value="AURANGABAD">AURANGABAD</option>
            <!-- cut for brevity -->
        </select>
    </div>
</div>

The label is an instruction outside of the options list, that tools will pick up and associate with the right list.

I see the appeal for people to have the instruction to be part of the drop down. And I wonder if there would be an accessible way to create this design. I wonder if an additional attribute on label instructing the browser to put inside as a non selectable item of the select list of option it targets with the for attribute.

Otsukare!

otsukare by Karl Dubost at

A moderate typhoon landed this week just above us. Winds in one direction. The peace of the eye of the typhoon. Finally the winds in the opposite direction. Magnificent. The day after it was a cemetery for insects. Tragedy. So it was mostly a week for old bugs cleaning.

The spectacle of the society, the society of spectacle. The turn of international events and the rise of arguments instead of discussions is mesmerizingly sad. Tune of the week: DJ Shadow feat. Run The Jewels - Nobody Speak

Webcompat Life

Progress this week:

Today: 2016-08-29T07:47:04.454102
295 open issues
----------------------
needsinfo       4
needsdiagnosis  83
needscontact    18
contactready    28
sitewait        146
----------------------

You are welcome to participate

Webcompat issues

(a selection of some of the bugs worked on this week).

  • option doesn't like display: none on Gecko at least. It hides the full list. I opened a new bug for Gecko. This is happening only in e10s windows. And there is already a patch in the making.
  • Not really a webcompat issue, but Google alerts breaking on small screens.
  • Sometimes bugs are not bugs. This is one delicate part of webcompat. Can we reproduce? Reproducing a bug is not always straightforward. It sometimes depends on the capabilities of your own devices (mobile AND desktop). But the cool thing is when the use is coming back and says "Hey sorry it seems to be working now." Thanks for this. It's very useful.

WebCompat.com dev

Reading List

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!

otsukare by Karl Dubost at

From the seventh floor, I see the cheminey of a local sento. It's not always on. The smoke is not coming out, it gives me a good visual feedback of the opening hours. It's here. It doesn't have notifications. It doesn't have ics, atom. It's just there. And it's fine as-is. The digital world seems sometimes to create complicated UI and UX over things which are just working. They become disruptive but not helpful.

Tune of the week: Leo Ferré - Avec le temps

Webcompat Life

Progress this week:

Today: 2016-08-22T13:46:36.150030
300 open issues
----------------------
needsinfo       4
needsdiagnosis  86
needscontact    18
contactready    28
sitewait        156
----------------------

You are welcome to participate

Webcompat issues

(a selection of some of the bugs worked on this week).

WebCompat.com dev

Reading List

  • Return of the 10kB Web design contest. Good stuff. I spend a good chunk of my time in the network panel of devtools… And it's horrific.

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!

otsukare by Karl Dubost at

Cicadas are an interesting insect. They live most of their time as a nymph under the ground in between 2 and 5 years, but some species live until 17 years before coming out and die six weeks after. What does it tell us about all the hidden work we put during our lifetime and blooms and shines for only a couple of hours.

Tune of the week: Ella Fitzgerald - Summertime (1968)

Webcompat Life

Progress this week:

Today: 2016-08-15T08:58:55.633182
298 open issues
----------------------
needsinfo       4
needsdiagnosis  80
needscontact    17
contactready    29
sitewait        158
----------------------

You are welcome to participate

Webcompat issues

(a selection of some of the bugs worked on this week).

  • Gecko and Blink/WebKit have different default CSS border-width values for the input element. It breaks a site. If we decide to fix it in Gecko, do we break other sites relying on this default value?
  • Performance issues on a heavy map Web site, though I'm not sure it is really a Web compatibility issue. It looks like more of something related to Gecko.
  • Another issue related to layout with a content inside a form. I need to dig a bit more.
  • no tap on priceline
  • Use chrome only for transcribeme
  • When using element.removeEventListener('event', callback) never forgets the second argument because it fails in Firefox, though that seems to be working in Chrome.
  • mask, background and mask-image difference creates immaterial design. The most important now being to really find what is the source of the issue.

WebCompat.com dev

  • Is invalid always the right keyword for closing an issue? From our side (project owner) it is invalid because it is not in the scope of the project, or there isn't enough details to reproduce. But from the user's perspective who had genuinely an issue (whatever the issue is), it can be felt as a strong rejection along the lines of "We don't care about you". Maybe we should find a better way of closing issues when they are out of scope.

Reading List

  • More a quote of the day, but spot on: > Wondering how long it will take for publishers to realize it’s Medium that desperately needs them and not the other way around.
  • And another one from Adam. And I really wish we could do that in a cool way! > <adam_s> Almost at our 3000th bug on webcompat.com. The lucky reporter who hits 3000 wins a broken light bulb

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!

Subscriptions