Each time I "set up my office" (moved to a new place for the next 3 months, construction work on the main home), I'm mesmerized by how easy it is to set up a work environment. Laptop, wifi and electricity are the main things needed to start. A table and a chair are useful but non essential. And eventually an additional screen to have more working surface to be comfortable. Basically in 5 minutes we are ready to work. And that's one chance of our area of work. How long does it take before you can start working?
Progress this week:
Today: 2016-07-25T06:21:33.702789 296 open issues ---------------------- needsinfo 5 needsdiagnosis 71 needscontact 14 contactready 34 sitewait 164 ----------------------
You are welcome to participate
(a selection of some of the bugs worked on this week).
- Time to time, people are reporting usability issues which are more or less cross-browsers. They basically hinder every browsers. It's out scope for the Web Compatibility project, but hint at something interesting about browsers and users perception. Often, I wonder if browsers should do more than just supporting the legacy Web site (aka it displays), but also adjust the content to a more palatable experience. Somehow the way, Reader mode is doing on user request, a beautify button for legacy content.
- Google Image Search and black arrow. A kind of cubist arrow for Firefox. Modern design?
- I opened an issue on Tracking Protection and Webcompat. Adam pointed me this morning to a project on moving tracking protection to a Web extension.
- Because we have more issues on Firefox Desktop and Firefox Android, we focus our energy there, so we need someone in the community to focus on Firefox OS issues.
- When I test Web sites on Firefox Android, I usually do it through the remote debugging in WebIDE and instead of typing a long URI on the device itself, I usually go to the console and paste the address I want
window.location = 'http://example.com/long/path/with/strange/356374389dgjlkj36s'.
- Starting to test a bit more in depth what
appearancemeans in different browsers. Specifically to determine what is needed for Web compatibility and/or Web standards.
- a WONTFIX which is a good news. Bug 1231829 - Implement
-webkit-border-imagequirks for compatibility. It means it has been fixed by the site owners.
- On this Find my phone issue on Google search, the wrong order of CSS properties creates a layout issue where the XUL
-moz-boxwas finally interpreted, but it triggered a good question from Xidorn. Should we expose the XUL
displayvalues to Web content? Add to that that some properties in the CSS never existed.
- hangout doesn't work the same way for Chrome and Firefox. There's something happening either on the Chrome side or the servers, which creates the right path of actions. I haven't determined it yet.
- Contribution Guidelines: we need to be more precise about the syntax of commits and pull requests.
- We have an issue about integrating gitcop into the project but I feel somehow it's already too late. I wish that gitcop was on the client side. There should be a way to configure git to be able to have syntax linters for commit messages. A couple of minutes later, I found a similar need that someone solved at Mozilla!
Follow Your Nose
- Document how to write tests on webcompat.com using test fixtures.
- ToWrite: Amazon prefetching resources with
<object>for Firefox only.