On Wed, May 21, 2014 at 3:59 AM, Anne van Kesteren wrote:
> On Tue, May 20, 2014 at 9:24 PM, Jonas Sicking wrote:
>> I think you are confusing issues. Or at least talking about two
>> separate issues at once in a way that I'm not sure what you are
>> talking about. The issue of "is there an XSS i
I question whether contentEditable=minimal should actually handle text
input. If the idea is to provide the base platform on which a developer
can build the editing product of their dreams, isn't text insertion just
another behavior they could potentially need to disable?
Stepping back, there are
That is a great article! “A good WYSIWYG editor of arbitrary HTML is just as
impossible as the halting problem is impossible... we have to treat it as an
editor platform and API, rather than as a standalone component that tries to do
everything itself.”
Let’s build a platform!
From: Julie Pare
Have you seen the recent post about the rich text editor that Medium uses?
It is a somewhat cheeky essay, including a mathematical proof, about how
contentEditable is broken. The conclusion is that in order to move
forward, we need to treat contentEditable as an API, rather than as a
standalone c
Great to hear! I’m working on an explainer document that will be more
descriptive than the short wiki docs I wrote a couple weeks ago. My thoughts on
your questions should be made clearer there. I’ll update this thread by the end
of the week with more details, and my initial thoughts are below.
On Wed, May 21, 2014 at 7:32 AM, Arthur Barstow wrote:
> [ Bcc www-tag ; Marc - please use public-webapps for IDB discussions ]
>
> On 5/20/14 7:46 PM, marc fawzi wrote:
>
>> Hi everyone,
>>
>> I've been using IndexedDB for a week or so and I've noticed that
>> cursor.advance(n) will always move n
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25854
Anne changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25853
Bug ID: 25853
Summary: "intentionally constraints"
Product: WebAppsWG
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25854
Bug ID: 25854
Summary: Throwing an error in XHR.setRequestHeader for
forbidden headers
Product: WebAppsWG
Version: unspecified
Hardware: PC
OS: Linux
On May 21, 2014, at 10:47 AM, Glenn Maynard wrote:
> Hmm. One factor that might change my mind on this: If I pass a blob URL,
> revoking the URL appropriately becomes hard. Even if it gets implemented,
> auto-revoke can't help with this. That brings back all of the problems with
> non-auto
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23780
Anne changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|---
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21264
Bug 21264 depends on bug 23780, which changed state.
Bug 23780 Summary: Check XMLHttpRequest and Notification don't break given the
new script settings object stuff
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23780
What|Remov
On 5/21/14 11:17 AM, Robin Berjon wrote:
I've been in several discussions on this topic over the past months, a
good example of which is:
https://twitter.com/tobie/status/457075677851037696
In reaction to that, I'm running an experiment to hold such
discussions in a manner that may prove
Hi Art, all,
On 21/05/2014 12:56 , Arthur Barstow wrote:
About two years ago I proposed in [1] creating a new list (f.ex.
public-webapps-devs) that is targeted toward developers using WebApps'
specs. Such a list would be used by developers using the APIs (as
opposed to implementers) as well as o
On Wed, 21 May 2014 16:27:36 +0200, Arthur Barstow
wrote:
On 5/21/14 7:02 AM, Anne van Kesteren wrote:
Developers seem to complain about us using mailing lists to
communicate rather than GitHub or some other centralized platform that
is not email. Might be worth checking with them first.
Y
On May 21, 2014 10:29 AM, "Arthur Barstow" wrote:
>
> On 5/21/14 7:02 AM, Anne van Kesteren wrote:
>>
>> Developers seem to complain about us using mailing lists to
>> communicate rather than GitHub or some other centralized platform that
>> is not email. Might be worth checking with them first.
>
Hmm. One factor that might change my mind on this: If I pass a blob URL,
revoking the URL appropriately becomes hard. Even if it gets implemented,
auto-revoke can't help with this. That brings back all of the problems
with non-auto-revoking blob URLs, and adds a new layer of complexity, since
I
[ Bcc www-tag ; Marc - please use public-webapps for IDB discussions ]
On 5/20/14 7:46 PM, marc fawzi wrote:
Hi everyone,
I've been using IndexedDB for a week or so and I've noticed that
cursor.advance(n) will always move n items forward regardless of
cursor direction. In other words, when th
On 5/21/14 7:02 AM, Anne van Kesteren wrote:
Developers seem to complain about us using mailing lists to
communicate rather than GitHub or some other centralized platform that
is not email. Might be worth checking with them first.
Yes, good point Anne. I tweeted this Q with some tags that were
On Wed, 21 May 2014 17:54:44 +0900, Zhang, Zhiqiang
wrote:
From: Hallvord R. M. Steen [mailto:hst...@mozilla.com]
Sent: Wednesday, May 21, 2014 4:22 AM
To: public-webapps
Subject: [web-platform-tests] where do tests for window.opener go?
Hi,
we have a window.opener issue and would like to ha
On Wed, May 21, 2014 at 12:56 PM, Arthur Barstow wrote:
> WDYT?
Developers seem to complain about us using mailing lists to
communicate rather than GitHub or some other centralized platform that
is not email. Might be worth checking with them first.
--
http://annevankesteren.nl/
On Tue, May 20, 2014 at 9:24 PM, Jonas Sicking wrote:
> I think you are confusing issues. Or at least talking about two
> separate issues at once in a way that I'm not sure what you are
> talking about. The issue of "is there an XSS issue with treated blob:
> like we treat data:" is a separate iss
Hi All,
About two years ago I proposed in [1] creating a new list (f.ex.
public-webapps-devs) that is targeted toward developers using WebApps'
specs. Such a list would be used by developers using the APIs (as
opposed to implementers) as well as other related purposes such as
announcing relev
> From: Hallvord R. M. Steen [mailto:hst...@mozilla.com]
> Sent: Wednesday, May 21, 2014 4:22 AM
> To: public-webapps
> Subject: [web-platform-tests] where do tests for window.opener go?
>
> Hi,
> we have a window.opener issue and would like to have some tests for it. I'm
> planning to write some
Sorry, but just a bit of follow up.
One may notice that the Web Components spec is imperative and assume that
declarative support is not important. But as it turns out, the notion of
using custom-elements to bootstrap declarative syntaxes allows various
parties to experiment in the real-world, as
25 matches
Mail list logo
