canmove, Confirmed users, Bureaucrats and Sysops emeriti
1,093
edits
DevTools/2011-05/05: Difference between revisions
no edit summary
No edit summary |
No edit summary |
||
| Line 49: | Line 49: | ||
* Style Editing | * Style Editing | ||
* HTML tree | * HTML tree | ||
** wants to prototype the editing outside of Firefox | |||
** editing prototype is close to working | |||
** next step is to integrate prototype in | |||
** next week getify is in Italy for a conference so he'll be working more intermittently | |||
== Roundtable == | == Roundtable == | ||
| Line 58: | Line 62: | ||
** remote debug protocol also has some e10s issues, dcamp will report back on that next week | ** remote debug protocol also has some e10s issues, dcamp will report back on that next week | ||
* Shipping for Firefox 6 | * Shipping for Firefox 6 | ||
** about 3 weeks left | |||
** some web console bug fixes/improvements | |||
** Scratchpad | |||
** The Command Line (likely preffed off) | |||
** Style Editor? possible | |||
* Alex would like some more use cases for the Scratchpad (rcampbell to look at) | |||
* Web performance WG is talking about "page visibility" | |||
** document-level state that tells the JS whether the page is visible at the moment (minimized, background tab, etc.) | |||
** also talking about an in-between state "preview" state as well | |||
** do we suspend JS when the browser is not visible? | |||
*** dcamp thinks we might raise the minimum resolution on timers, but not otherwise | |||
** wg wants a global property that reflects the visibility of the window (though they are concerns about privacy/security) | |||
** seems like a question for dev-platform | |||
* JSConf | * JSConf | ||
** Modules and other JS.next features | ** Modules and other JS.next features | ||
** Chrome devtools notes | ** Chrome devtools notes | ||
* Code editing in the tree | |||
** discussion on dev-platform | |||
** Ehsan was anti-Ace because of issues around a10y and i18n | |||
** Orion came up as an alternative | |||
** Orion license is compatible | |||
** Could we use the built-in editor (contenteditable)? | |||
** rcampbell wants to set up a meeting with Ehsan to talk about the gaps | |||
** dcamp mentioned the developer mindprint of our codebase... having too many editors is too difficult for people to keep in mind | |||
** rcampbell will set up a meeting with Ehsan to discuss editors | |||
** our goal is to get something in the tree soon that provides a good editing experience and meets a10y and i18n needs. | |||
* Web Console bugs | * Web Console bugs | ||
** Spoke about Browser Console | |||
*** The idea is ultimately to replace the Error Console with something that works more like the Web Console but is all about displaying chrome bugs | |||
** three high-value relatively low-cost bugs: | |||
** {{bug|644419}} limits per category | |||
** {{bug|622303}} remember filter settings | |||
** {{bug|634406}} Select All results in multiline input | |||
** go after those three and then fleshing out of console object | |||