ist, ,
and please, prefix the subject line with
[css-cascade-4]
(as I did on this message).
For the CSS WG,
~fantasai
is message).
For the CSS WG,
~fantasai
eally useful to solve this problem either with a CSS
property like -webkit-appearance or decorator.
Perhaps Tantek or Fantasai could enlighten us.
Relevant URLs:
https://www.w3.org/Search/Mail/Public/search?type-index=www-style&index-type=t&keywords=appearance&search=Search
https://lists.w3
from the boilerplate.
It probably makes sense to do that anyway. They should both point to the
currently-maintained draft.
~fantasai
line with
[css-scoping]
(as I did on this message).
For the CSS WG,
~fantasai
ailing list [1],
, and please, prefix the subject line with
[css-cascade-3]
(as I did on this message). The deadline for comments is
** 26 August 2013 **
Please let us know if you need an extension.
We would particularly appreciate review of this module from the
HTML and WebAPI communities. Thanks!
For the CSS WG,
~fantasai
On 04/03/2013 06:39 PM, fantasai wrote:
http://www.w3.org/TR/selectors-api2/#the-scope-pseudo-class
This section has already been copied to Selectors 4 (and has been
for awhile, actually), so should be removed here and replaced with
references to Selectors 4.
http://www.w3.org/TR/selectors4
v.w3.org/csswg/selectors4/#scoping
Please let us know if there are any errors.
We'll try to publish a new WD soon with the updated definitions.
~fantasai + TJ
with the topic of your comment, as I have done here.
Thanks!
~fantasai
, particularly on the changes.
Please send any comments to this mailing list, , preferably
starting a new thread, and please, prefix the subject line with
[selectors4]
(as I did on this message).
For the CSS WG,
~fantasai
inherit from
anything, what is it's value? This is not defined, because currently in
CSS every element has a parent except the root, and there is a special
exception to inheritance specifically for the root element.
~fantasai
On 06/21/2012 04:18 AM, Arthur Barstow wrote:
On 6/21/12 5:16 AM, ext Anne van Kesteren wrote:
On Tue, Jun 19, 2012 at 10:48 PM, fantasai
wrote:
You could just work in the explanation I sent in
http://www.w3.org/mid/4fc64100.3060...@inkedblade.net
Added a note.
The reason this is not very
On 06/19/2012 12:49 AM, Daniel Glazman wrote:
Le 19/06/12 09:41, Anne van Kesteren a écrit :
On Tue, Jun 19, 2012 at 1:45 AM, fantasai wrote:
It looks like you missed #2.
I think ::backdrop is clear enough. Not entirely sure what you would
expect seeing there more than what it already says
On 06/19/2012 12:40 AM, Anne van Kesteren wrote:
On Tue, Jun 19, 2012 at 1:31 AM, fantasai wrote:
On 06/01/2012 05:02 AM, Anne van Kesteren wrote:
On Wed, May 30, 2012 at 5:47 PM, fantasai
wrote:
Though it seems likely that 'fixed' is required here, no?
The top layer concept is
the latest ED
<http://dvcs.w3.org/hg/fullscreen/raw-file/tip/Overview.html> address the above
concerns?
It looks like you missed #2.
~fantasai
Sorry, looks like I accidentally dropped webapps from the CC list. Sending
again...
On 06/01/2012 05:02 AM, Anne van Kesteren wrote:
On Wed, May 30, 2012 at 5:47 PM, fantasai wrote:
Though it seems likely that 'fixed' is required here, no?
The top layer concept is also used by HT
On 05/30/2012 08:47 AM, fantasai wrote:
Other comments:
Oh, also, you need a reference to CSS2.1, otherwise your rendering section
isn't defined. :)
~fantasai
licit about what does and does not apply, at least
in terms of CSS2.1 properties.
Other comments:
# *|*:fullscreen {
# position:fixed;
# top:0; right:0; bottom:0; left:0;
# margin:0;
Shouldn't that be margin: auto? I'd've assumed you'd want replaced elements
centered by default.
~fantasai
On 11/22/2011 05:30 AM, Lachlan Hunt wrote:
On 2011-11-22 14:09, Boris Zbarsky wrote:
On 11/22/11 8:05 AM, Lachlan Hunt wrote:
The current draft of Selectors 4 includes :matches(), though, which can
partially handle that case, excluding :not([type]), which would have to
be left separate.
That
~fantasai
20 matches
Mail list logo
