Boris Zbarsky wrote:
On 3/24/11 9:29 PM, Nicholas Zakas wrote:
[...]
Fixing the issue results in:
div
style scoped.foo { color: red; }/div
/div
The correct fix for this issue is to put this style in the head,
isn't it? Why would would you fix it by adding @scoped?
There is nothing
On 03/25/2011 05:24 AM, Koji Ishii wrote:
Thank you for the reply.
Anyway, do you have any concern about the behaviors of the current browsers?
No, not as of now particularly. Neither I know how UAs are going to implement
require that authors not let authors enter values longer than the
All,
there are now two different sets of APIs public, one documented in the spec
(http://www.whatwg.org/specs/web-apps/current-work/multipage/dnd.html#video-conferencing-and-peer-to-peer-communication)
and one sent the other day
I agree that the WHATWG draft looks clearer at first glance. Having
two different proposals of such similar nature requires everyone
interested in them to read and digest before figuring out how they
differ specifically. And there would be differences in understanding
which can cause further
On 2011-03-22 11:01, Stefan Håkansson LK wrote:
On 2011-03-18 05:45, Ian Hickson wrote:
All of this except selectively muting audio vs video is currently
possible in the proposed API.
The simplest way to make selective muting possible too would
be to change
how the pause/resume thing works in
The part of the spec that defines what browsers are supposed to do
already reflects current browser behavior.
Can you point me to that?
And if the spec already specifies the current browser behavior, why does the
definition of style require the scoped attribute in flow content? This seems
On Thu, Mar 24, 2011 at 12:31 AM, Ehsan Akhgari eh...@mozilla.com wrote:
This is what Gecko does in Firefox 4. Webkit, however, implements the
non-space-eating approach on all platforms. I think this is an advantage,
because it means that the consumers of the API can rely on the behavior of
On 3/25/11 12:53 PM, Nicholas Zakas wrote:
The part of the spec that defines what browsers are supposed to do
already reflects current browser behavior.
Can you point me to that?
http://www.whatwg.org/specs/web-apps/current-work/multipage/semantics.html#attr-style-scoped
second paragraph:
On Thu, Mar 24, 2011 at 9:29 PM, Nicholas Zakas nza...@yahoo-inc.com wrote:
It seems like the scoped attribute should be optional when style is used as
flow content and disallowed when used in meta content. That way, you're
adding the new functionality of limiting styles to a subtree while
I have two more questions about the Stream API:
1. Are GeneratedStream objects supposed to stop when they go out of
scope?
2. Should StreamRecorder objects keep alive the Stream objects that
created them? Is there a use case where this should not be the case?
On 17 March 2011
On Wed, Mar 23, 2011 at 8:18 PM, TAMURA, Kent tk...@chromium.org wrote:
Ok. It seems the best solution is to just remove the suffering from being
too long state and simply require that authors not let authors enter
values longer than the maxlength. Right?
I agree removing tooLong validity.
On 03/25/11 15:25, Satish Sampath wrote:
I agree that the WHATWG draft looks clearer at first glance. Having
two different proposals of such similar nature requires everyone
interested in them to read and digest before figuring out how they
differ specifically. And there would be differences in
Boris Zbarsky bzbar...@mit.edu schrieb am Fri, 25 Mar 2011 13:56:00
-0400:
[…]
We could argue about this of course; this is why I asked for use
cases. The use case of putting style without @scoped right at the
start of body is a good one, and I think that should be allowed...
How is that
13 matches
Mail list logo
