On 2014-08-12 17:23, Boris Zbarsky wrote:
On 8/12/14, 9:26 AM, Anne van Kesteren wrote:
I somewhat prefer always uppercasing, but that would require changes
to XMLHttpRequest.
Gecko used to have the always uppercasing behavior for XHR and people
complained about it until we aligned with the
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26673
Anne ann...@annevk.nl changed:
What|Removed |Added
Status|NEW |RESOLVED
Pretty good docs, Ben.
I have comments mostly about Issue 2
(http://w3c.github.io/editing-explainer/#h_issue_2).
As long as actions are well documented, browsers can provide defaults that will
fit 90% of the *good quality* content creation requirements out there.
Additionally just
On Mon, Sep 8, 2014 at 6:05 PM, Frederico Knabben f.knab...@cksource.com
wrote:
snip
IMHO, the following are the minimal features that it should provide:
- Selection: UI (e.g. caret), creation (e.g. mouse) and modifications
(e.g. arrows)
- Focus (probably part of Selection, but it's so
On 2014/09/04 13:33, Marcos Caceres wrote:
...
A developer can then have a Let's get started! screen, where they explain
why they need each feature before they request it.
...
Absolutely. I the above, a dev could still ask for each API as needed. Like:
Ok, let's get your camera working.
