Summer in its full heat has started in Japan. I'll follow the sun, Beatles.
Webcompat Life
Progress this week:
Today: 2016-07-11T09:55:26.360775
346 open issues
----------------------
needsinfo 5
needsdiagnosis 74
needscontact 33
contactready 50
sitewait 165
----------------------
You are welcome to participate
We had a short team meeting.
Webcompat issues
(a selection of some of the bugs worked on this week).
- offsetWidth creates issue on this site. Hallvord may have found the origin of the issue. It would require a test case to show the differences in between Blink, Edge and Gecko to be extra-sure. The definition of offsetWidth in Gecko:
NS_IMETHOD GetOffsetWidth(int32_t *aOffsetWidth) = 0;which leads to OffsetWidth() BUT Daniel found the culprit. This is fixed in Aurora and Nightly so will be soon working on production releases. - Google Search and Firefox Android (when faking the user agent to be Chrome) is giving an almost working site. There's only one issue when requesting images on the tab. Almost there. Note that this is already working in Firefox Nightly because of the implementation of some WebKit properties.
WebCompat.com dev
- I finally came around fixing a "bug" when rewriting Link headers I had introduced in webcompat.com and that one of our interns discovered when solving another issue.
- Fixed our contributions guidelines to be a bit stricter on the Pull Request review policy. Summary: You should not merge if you are the pull request submitter and the pull request needs an r+ before expecting to move forward.
- Started to work on a logging feature for webcompat.com to detect potential abuse of the service. For now, let's not over-engineer it and make it very simple. It requires the service for log rotation and keep only the last two weeks, and the actual logging in Flask, and also a change of policy.
- Also trying to make a bit more square the repo for issue parsing so that external people can participate. This is in progress.
- When interacting a lot with GitHub, I was thinking it would be nice to have an up-to-date mocking python module of GitHub API. Maybe that could be done by parsing the API documentation and extracting the tables and responses and then creating the mocking service. Just food for thoughts. Even better would be github giving a JSON file describing all routes, HTTP codes, and responses.
Reading List
- Rust and Rest. Replace REST by HTTP in that article and it's a nice read.
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!