On Mon, Jun 14, 2010 at 7:27 AM, Anne van Kesteren wrote:
> On Thu, 27 May 2010 18:22:03 +0200, Aaron Boodman wrote:
>>
>> On Thu, May 27, 2010 at 5:09 AM, Lachlan Hunt
>> wrote:
>>>
>>>
>>
>> You're right -- that one does exist already within the page. And it is
>> a shame to waste these exist
On Sat, Aug 21, 2010 at 6:18 PM, Brenton Strine wrote:
>>
>
> and
>
>>
>
> are effective, but then again this would be too:
>
> ...*
>
> It just seems a shame that we have this neat attribute that indicates
> required controls, but we can't actually use it to change the
> presentation adding ad
Someone on wha...@whatwg.org:
> This question is sort of CSS related, but I think it's worth bringing up
> here, assuming it hasn't already been discussed.
I’m cross-posting to www-style, please follow-up there.
> [required]:after {content:"*";}
>
> Name
>
If we ignore the possibility of anon
>
and
>
are effective, but then again this would be too:
...*
It just seems a shame that we have this neat attribute that indicates
required controls, but we can't actually use it to change the
presentation adding additional code.
Brenton
On Sat, Aug 21, 2010 at 2:00 AM, Robert O'Callahan wrote:
> On Sat, Aug 21, 2010 at 5:21 PM, Adam Barth wrote:
>> How is going fullscreen different from opening a popup window?
>
> That depends on how the UA chooses to handle it. But this proposed
> fullscreen API is based on the idea that the fu
On Fri, Aug 20, 2010 at 11:33 PM, WhatWg wrote:
> However, it seems that since input is an empty element, the content cannot
> be added after.
Right; s don't have children. (In some actual implementations,
they just automatically hide their children from the rest of the DOM.)
~TJ
Hardly an expert in this field, but wouldn't implementing media tags
(video and audio) a tad like websockets be a good idea. Using the tag
should add a special header that says it can upgrade conneciton to
something like "media" which constantly lets client have duplex
conversation with the server,
This could be another way to solve the same problem:
label + input[required] + span:after { content: " * "; }
Name
However, the above does not work on IE6 (attribute selectors).
So the id/class suggested by Chris is actually the most cross-browser
solution.
Diego
On Sat, Aug 21, 2010 at 3
> Why not make "required" an acceptable attribute for the label element?
The class or title attribute can solve your problem:
label.required:after {content:"*"}
label[title~="required"]:after {content:"*"}
Sorry, forget about this question.
I have managed to get it working after all.
Apologies,
Silvia.
On Sat, Aug 21, 2010 at 5:54 PM, Silvia Pfeiffer
wrote:
> Hi all,
>
> I've tried to work with the globalCompositeOperation [1] over the last days
> for a particular use case where I am trying to use
On Sat, Aug 21, 2010 at 5:21 PM, Adam Barth wrote:
> How is going fullscreen different from opening a popup window?
>
That depends on how the UA chooses to handle it. But this proposed
fullscreen API is based on the idea that the fullscreen content "takes over"
the toplevel browsing context to w
Hi all,
I've tried to work with the globalCompositeOperation [1] over the last days
for a particular use case where I am trying to use a gradient to merge with
a canvas as a mask. I now wonder if the globalCompositeOperation is indeed
meant to be used this way and what transparency means.
For exa
12 matches
Mail list logo
