On Thu, Jan 22, 2015 at 2:18 AM, Glen Huang wrote:
> This algorithm shouldn’t slow normal operations down, and I wonder if the
> spec could use an algorithm like this and not using document fragment.
I looked at this again and we do want to use a DocumentFragment.
Otherwise mutation observers ge
I recommend that we change the "dir" attribute to "directories" and keep
"directory" the same as it is now to avoid clashing with the existing "dir"
attribute on the HTMLInputElement. All in favor?
As for the behavior of setting the "directories" attribute on a file input, we
have the following
https://twitter.com/shimonamit/status/571046844488245248
Not very surprising. It is a very good idea even if the current solution in Chrome is a
bit of a prototype since it is not the extension (which BTW is redundant) that needs to
be vetted and "app-stored"; it is the native application that
> On May 4, 2015, at 10:20 PM, Anne van Kesteren wrote:
>
>> On Tue, May 5, 2015 at 6:58 AM, Elliott Sprehn wrote:
>> We can solve this
>> problem by running the distribution code in a separate scripting context
>> with a restricted (distribution specific) API as is being discussed for
>> other
On Mon, May 4, 2015 at 9:38 PM, Anne van Kesteren wrote:
> On Tue, May 5, 2015 at 2:08 AM, Tab Atkins Jr. wrote:
>> On Thu, Apr 30, 2015 at 10:51 PM, Anne van Kesteren wrote:
>>> But maybe you're right and the whole
>>> pseudo-class/pseudo-element distinction is rather meaningless. But at
>>> le
On Mon, May 4, 2015 at 9:52 PM, Jonas Sicking wrote:
> On Sun, Apr 26, 2015 at 8:37 PM, L. David Baron wrote:
>> On Saturday 2015-04-25 09:32 -0700, Anne van Kesteren wrote:
>>> I don't understand why :host is a pseudo-class rather than a
>>> pseudo-element. My mental model of a pseudo-class is t
On Tue, May 5, 2015 at 11:20 AM, Ryosuke Niwa wrote:
>> On May 4, 2015, at 10:20 PM, Anne van Kesteren wrote:
>>
>>> On Tue, May 5, 2015 at 6:58 AM, Elliott Sprehn wrote:
>>> We can solve this
>>> problem by running the distribution code in a separate scripting context
>>> with a restricted (dis
On Mon, May 4, 2015 at 8:52 PM, Lea Verou wrote:
> Sorry for reviving such an old thread (almost 3 years now!) but I recently
> came across a huge use case for CAS: Semantic data! Namely, Microdata and
> RDFa. They’re both applied using attributes, which makes them super tedious
> to add to exist
On Mon, May 4, 2015 at 10:42 PM, Anne van Kesteren wrote:
> Over in
> https://lists.w3.org/Archives/Public/public-whatwg-archive/2015May/0006.html
> Jonas pointed out that having two APIs for doing the same thing is
> "nuts". We should probably decide whether we go ahead with the
> Permissions AP
On Tue, May 5, 2015 at 2:54 PM, Jonas Sicking wrote:
> On Mon, May 4, 2015 at 10:42 PM, Anne van Kesteren
> wrote:
> > Over in
> https://lists.w3.org/Archives/Public/public-whatwg-archive/2015May/0006.html
> > Jonas pointed out that having two APIs for doing the same thing is
> > "nuts". We shou
> On May 5, 2015, at 11:55 AM, Tab Atkins Jr. wrote:
>
> On Tue, May 5, 2015 at 11:20 AM, Ryosuke Niwa wrote:
>>> On May 4, 2015, at 10:20 PM, Anne van Kesteren wrote:
>>>
On Tue, May 5, 2015 at 6:58 AM, Elliott Sprehn
wrote:
We can solve this
problem by running the dist
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28614
Bug ID: 28614
Summary: Weaken the requirement of the time of running async
steps
Product: WebAppsWG
Version: unspecified
Hardware: All
OS: All
On Wed, May 6, 2015 at 12:32 AM, Mike West wrote:
> I agree with Jonas. Extending the permission API to give developers a single
> place to check with a single consistent style seems like the right way to
> go.
Yet others at Google are pushing the expose them twice strategy...
Perhaps because the
On Wed, May 6, 2015 at 3:22 AM, Ryosuke Niwa wrote:
> Where? I have not yet to see a use case for which selective redistribution
> of nodes (i.e. redistributing only a non-empty strict subset of nodes from an
> insertion point) are required.
Isn't that what e.g. does? That is, only cares abo
On Tue, May 5, 2015 at 8:39 PM, Tab Atkins Jr. wrote:
> It's certainly no weirder, imo, than having a pseudo-element that
> doesn't actually live in any element's pseudo-tree, but instead just
> lives in the normal DOM, but can only be selected by using a
> pseudo-element selector with no LHS. Ps
15 matches
Mail list logo
