canmove, Confirmed users
432
edits
Firefox/Australis Meeting Notes: Difference between revisions
Firefox/Australis Meeting Notes (view source)
Revision as of 19:11, 31 October 2013
, 31 October 2013→next meeting: add 10/13
(→next meeting: Add 10/24 notes) |
(→next meeting: add 10/13) |
||
| Line 4: | Line 4: | ||
= next meeting = | = next meeting = | ||
([https://fx-team.etherpad.mozilla.org/australis-meeting-notes next meeting has not yet occurred]) | ([https://fx-team.etherpad.mozilla.org/australis-meeting-notes next meeting has not yet occurred]) | ||
=10/31/2013= | |||
* Milestone 9 | |||
** http://i.imgur.com/YIKZEQ8.gif | |||
* Perf regression and other landing blockers | |||
** bug 902024 (TART regression) | |||
*** Bug 921038 - Move selected tab curve clip-paths into SVG-as-an-image so it is cached | |||
**** This has landed, and the Win XP TART regression has been neutralized. EAT IT TART. | |||
*** Bug 924415 - Find out why setting chromemargin to 0,-1,-1,-1 is so expensive for TART on UX branch on OS X. | |||
**** jrmuizel and mconley are hacking on this. We're trying to tighten the feedback loop with a Mac Mini here in the Toronto office that we're trying to match to the talos slave specs. | |||
**** We've got some leads, but it's kinda slow going on this. | |||
** tart data: https://docs.google.com/a/mozilla.com/spreadsheet/ccc?key=0Asj8iLTl0K0UdGJzVnVYYkJTSDREbndRWWFTLWNyS1E | |||
* Bug tracking (10/24 to 10/31) | |||
** Did a triage today, week-over-week bug numbers are out of whack because of it, but we will be in a better position for the foreseeable future | |||
** P1: -1 | |||
** P2: +12 | |||
** P3: +5 | |||
** P4: -7 | |||
** P5: -30 | |||
** http://screencast.com/t/izZDiBr1j | |||
** https://docs.google.com/a/mozilla.com/spreadsheet/ccc?key=0AiPXmmKgSs8udHgzcEhqd0tkTXlJRU8zcXFzMEhneHc | |||
** | |||
* Roundtable | |||
** mikedeboer panel screenshots | |||
*** http://note.io/HhvBrM | |||
*** http://note.io/HhvJrg | |||
*** http://note.io/HhvRqI | |||
* Action Items (Last Week) | |||
** bwinton: Get a list of what we want to build in an a11y sense. | |||
*** To block on a11y we'd need to see a medium-large regression in what people can access, | |||
**** but since we still have the menu, there should be no regression in access | |||
**** therefore, no blocking. | |||
*** The old menu button wasn't accessible. | |||
**** It would be nice if the new one was. | |||
**** The main audience is likely sighted non-mouse users. | |||
**** So we want control navigation with clear visual indication. | |||
**** There is something higher order than tab navigation …. F6 navigation | |||
***** We could put the menu button in F6 navigation sequence. | |||
**** Guidelines at http://access.aol.com/dhtml-style-guide-working-group/#menu | |||
*** Customization mode is less concerning. | |||
**** When we do it, context menu and/or cut-and-paste operation would be good. | |||
*** ------- tl;dr below this line. ------- | |||
*** Things we should really do: | |||
**** Let users get to the notification bar at the bottom with F6. | |||
**** Let users get to the Site Identity icon/Camera Permission doorhanger/etc popup. | |||
**** Let users change the search provider. | |||
**** In high-contrast mode on Windows (the purple version), a lot of text is light-on-light. HC mode is generally kind of bad (eg bug 790706) | |||
*** Things we might want to do: | |||
**** Add the menu panel to the F6 navigation order or invoke with a keyboard shortcut. | |||
**** Let people use the arrow keys to navigate around the menu. | |||
***** left/right work now | |||
***** up/down do the same as left/right instead of moving up and down. | |||
***** The cut/copy/paste and zoom bars aren't reachable. | |||
**** Show the focus ring on the menu panel if the user uses keyboard nav in it. | |||
**** Show the focus ring on the menu panel if launched via the keyboard shortcut. | |||
**** Make the context menus work the way we think they should. (bug 870471) | |||
** bwinton & mconley: Sort out what the end state of customization mode smoothness is. | |||
*** We've got a reference Macbook that we're using, and mconley wrote a tool to analyze how many frames we're getting during the transition (3), and how many we want for 60fps (9). So that's our target. | |||
**** Now that we have this office Mac Mini though, we might want to switch to this hardware though... | |||
** madhava et al should file bugs for unfiled things from the Australis-finalpass etherpad | |||
*** all specific notes should have a bug number now, some of them need more specific info (e.g. Menupanel icon shifting behaviour) - https://firefox-ux.etherpad.mozilla.org/Australis-finalpass | |||
**** (listed an existing bug for the menupanel shifting behaviour) | |||
* Action Items (New) | |||
** bwinton to file accessibility bugs where it makes sense. | |||
** bwinton to write a prototype that does something with tabs and animation… | |||
*** We were thinking of trying to snap the width of the tabstrip and nav-bar at the beginning of the transition so that these two elements don't have to transition their width during the ... transition. | |||
= 10/24/2013 = | = 10/24/2013 = | ||