Am 16.05.2011 21:20 schrieb Aryeh Gregor:
On Mon, May 16, 2011 at 9:33 AM, Markus Ernstderer...@gmx.ch wrote:
I have seen content management systems where text editors tweak the enter
key to behave the same also in non-IE UAs (e.g. if you use Contenido with
TinyMCE, Firefox produces the same
Am 13.05.2011 12:00 schrieb Michael A. Puls II:
On Thu, 12 May 2011 16:28:47 -0400, Aryeh Gregor
simetrical+...@gmail.com wrote:
Another problem with p is that it's very easy to create
unserializable DOMs with it. I've seen cases where at least some
browsers will put things inside p that will
On Mon, 16 May 2011 17:59:43 +0200, Remy Sharp r...@leftlogic.com wrote:
Hi all,
Since this is *my* code that we're talking specifically about, I'd like
to repeat Glenn's point that this is not sloppy code (the cheeky shit),
and that the /everyman/ developer is going to think that
Hello
While discussing about contenteditable elements, the WYSIWYG aspect was
mentioned. For real WYSIWYG in a text editor of a CMS, Blog, Forum or
whatever, it would be necessary for the contents of the contenteditable
element to:
- Disable the styles of the surrounding page
- Enable the
On 17 May 2011, at 09:04, Philip Jägenstedt wrote:
Or do you mean a spec bug?
I meant a spec bug :)
On Tue, 17 May 2011 10:47:02 +0200, Remy Sharp r...@leftlogic.com wrote:
On 17 May 2011, at 09:04, Philip Jägenstedt wrote:
Or do you mean a spec bug?
I meant a spec bug :)
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12664
Still, I don't think just advocacy is any kind of solution.
On Tue, May 17, 2011 at 1:09 AM, Markus Ernst derer...@gmx.ch wrote:
Special cases:
- If the linked CSS document contains declarations for the body element,
they are applied to the contenteditable element itself. (This could be
necessary in case of light text on dark backgrounds, where you
On Tue, May 17, 2011 at 5:09 AM, Philip Jägenstedt phil...@opera.comwrote:
To target this specific pattern, one hypothetical solution would be to
special-case the first script that attaches event handlers to a video
element. After it has run, all events that were already fired before the
On 5/17/11 11:23 AM, Tab Atkins Jr. wrote:
On Tue, May 17, 2011 at 1:09 AM, Markus Ernstderer...@gmx.ch wrote:
Special cases:
- If the linked CSS document contains declarations for the body element,
they are applied to the contenteditable element itself. (This could be
necessary in case of
On Tue, May 17, 2011 at 11:05 AM, Boris Zbarsky bzbar...@mit.edu wrote:
On 5/17/11 11:23 AM, Tab Atkins Jr. wrote:
On Tue, May 17, 2011 at 1:09 AM, Markus Ernstderer...@gmx.ch wrote:
Special cases:
- If the linked CSS document contains declarations for the body element,
they are applied to
On 5/17/11 2:40 PM, Tab Atkins Jr. wrote:
Doesn't really matter to me; either seems sensical. :root has the
benefit of existing. ^_^
:scope has the benefit of making more sense (and happens to exist in my
tree, is used in the proposed selectors API, etc).
-Boris
On Tue, May 17, 2011 at 9:09 PM, Philip Jägenstedt phil...@opera.comwrote:
To target this specific pattern, one hypothetical solution would be to
special-case the first script that attaches event handlers to a video
element. After it has run, all events that were already fired before the
On Wed, May 18, 2011 at 7:09 AM, Robert O'Callahan rob...@ocallahan.orgwrote:
Sure! For certain kinds of events (load, the video events, maybe more),
delay the firing of such events until, say, after DOMContentLoaded has
fired. If you're careful you might be able to make this a strict subset
On Tue, May 17, 2011 at 3:04 AM, Markus Ernst derer...@gmx.ch wrote:
If the behavior is settable, it might even be a good idea to leave the
choice of the standard behavior to the UAs. Authors who have a reason to
care can set their preferred behavior, while other authors might prefer to
leave
On Tue, May 17, 2011 at 12:50 PM, Aryeh Gregor simetrical+...@gmail.comwrote:
On Tue, May 17, 2011 at 3:19 AM, Ryosuke Niwa rn...@webkit.org wrote:
I completely disagree. As a user, I want semantics when I write my blog
entry on WordPress so that I can tweak presentation afterwards. e.g. I
Last week, a proof of concept of a previously theoretical timing
attack against WebGL was published which allows theft of cross-domain
images' content.
To address this vulnerability it appears to be necessary to ban the
use of cross-domain images and videos in WebGL. Unfortunately, doing
so will
On Tue, May 17, 2011 at 2:25 PM, Kenneth Russell k...@google.com wrote:
Last week, a proof of concept of a previously theoretical timing
attack against WebGL was published which allows theft of cross-domain
images' content.
To address this vulnerability it appears to be necessary to ban the
On Tue, May 17, 2011 at 5:40 PM, Jonas Sicking jo...@sicking.cc wrote:
If the supports credentials flag is set to false, the request will
be made without cookies, and the server may respond with either
Access-Control-Allow-Origin:* or Access-Control-Allow-Origin:
origin.
I propose that the
On Tue, May 17, 2011 at 2:52 PM, Glenn Maynard gl...@zewt.org wrote:
On Tue, May 17, 2011 at 5:40 PM, Jonas Sicking jo...@sicking.cc wrote:
If the supports credentials flag is set to false, the request will
be made without cookies, and the server may respond with either
On 5/17/11 6:48 PM, Aryeh Gregor wrote:
On Tue, May 17, 2011 at 12:37 AM, Robert O'Callahan
rob...@ocallahan.org wrote:
Amazingly, our line breaking rationale is actually quite well documented!
https://wiki.mozilla.org/Gecko:Line_Breaking
Some comments on UAX#14:
On Tue, May 17, 2011 at 6:11 PM, Ian Hickson i...@hixie.ch wrote:
On Tue, 17 May 2011, Kenneth Russell wrote:
Last week, a proof of concept of a previously theoretical timing attack
against WebGL was published which allows theft of cross-domain images'
content.
To address this vulnerability
21 matches
Mail list logo
