>
> You can see that the overflows the paragraph in both Firefox and
> WebKit. This seems to be caused by the align="left", which I believe
> implies the CSS style "float: left;". I suspect that floats do not get
> counted towards the height of a block, but I'd have to check. I suspect
> that i
I still don't understand the "problem" here? The bug you mentioned was
marked invalid. As far as I can tell our current float behavior is correct.
-eric
On Wed, May 18, 2011 at 12:35 AM, Mustafizur Rahaman
wrote:
> You can see that the overflows the paragraph in both Firefox and
>> WebKit.
Why does webkit not provide support for native CSS3 attributes in its
parsing engine where those attributes clearly coincide with most other
browsers' attributes -and- the Candidate Recommendations set forth by W3?
Let me put it this way: What is the purpose of every browser having
their own
On May 18, 2011, at 6:36 AM, Sabri Aurrelia wrote:
> Why does webkit not provide support for native CSS3 attributes in its parsing
> engine where those attributes clearly coincide with most other browsers'
> attributes -and- the Candidate Recommendations set forth by W3?
>
> Let me put it this
Though, in this case, the spec is at CR and has been since 2009. Is there an
additional process to removing the vendor prefixes for WebKit? So, are they
still there because no one bothered to remove them, or because the consensus
is they should remain for some reason?
--Brady
On Wed, May 18, 2011
The best way to move forward would be to file a bug requesting that the
prefixes be removed.
Simon
On May 18, 2011, at 9:31 AM, Brady Duga wrote:
> Though, in this case, the spec is at CR and has been since 2009. Is there an
> additional process to removing the vendor prefixes for WebKit? So,
I've recently been spending some time reviewing some of the WebKit
port that are not part of the core WebKit archive. Electronic Arts,
for example, has been very good about making source dumps of their
build of WebKit available (wow -- WebKit on the PS3! :), Playo has
released their sources, and V
I hope i'm sending this mail to the right address, forgive me if i'm wrong..
i selected JavascriptCore over the competition because i read that
it's thread safe.
but, i can't get it to work from within threads with crashing.
the first version of my test was using one context, created with
JSGlob
Hi Martijn.
> i selected JavascriptCore over the competition because i read that
> it's thread safe.
Yes, with certain restrictions, JavaScriptCore can be used concurrently on
multiple threads.
> but, i can't get it to work from within threads with crashing.
It's hard to diagnose exactly what'
On Wed, May 18, 2011 at 12:36 PM, Brent Fulgham wrote:
> Google
> used this same approach with their Chromium port, the side effects of
> which find us in year two (or three?) of the effort to merge those
> changes back into the core WebKit archive.
>
Um, what? The Chromium port is fully upstre
Hi Peter,
On Wed, May 18, 2011 at 2:09 PM, Peter Kasting wrote:
>> Google used this same approach with their Chromium port, the side effects of
>> which find us in year two (or three?) of the effort to merge those
>> changes back into the core WebKit archive.
>
> Um, what? The Chromium port is f
On Wed, May 18, 2011 at 2:25 PM, Brent Fulgham wrote:
> Hi Peter,
>
> On Wed, May 18, 2011 at 2:09 PM, Peter Kasting
> wrote:
> >> Google used this same approach with their Chromium port, the side
> effects of
> >> which find us in year two (or three?) of the effort to merge those
> >> changes b
On Wed, May 18, 2011 at 2:35 PM, Ojan Vafai wrote:
> On Wed, May 18, 2011 at 2:25 PM, Brent Fulgham wrote:
>
>> Hi Peter,
>>
>> On Wed, May 18, 2011 at 2:09 PM, Peter Kasting
>> wrote:
>> >> Google used this same approach with their Chromium port, the side
>> effects of
>> >> which find us in y
Done: https://bugs.webkit.org/show_bug.cgi?id=61096
On Wed, May 18, 2011 at 9:36 AM, Simon Fraser wrote:
> The best way to move forward would be to file a bug requesting that the
> prefixes be removed.
>
> Simon
>
>
> On May 18, 2011, at 9:31 AM, Brady Duga wrote:
>
> Though, in this case, the sp
Hello Geoff,
Thank you for your bug filing. I fixed it yesterday.
Thanks,
gyuyoung
> Hi folks.
>
> The EFL builder is sick.
>
> I've filed https://bugs.webkit.org/show_bug.cgi?id=61018 explaining how to
> fix it, but I'm just not familiar enough with the EFL build system to do
> so myself.
>
Is this a bug?
-- Forwarded message --
From: Boris Zbarsky
Date: Wed, May 18, 2011 at 7:32 PM
Subject: Re: [whatwg] More HTML Editing Commands questions
To: wha...@lists.whatwg.org
On 5/18/11 6:57 PM, Tim Down wrote:
> On 18 May 2011 19:32, Aryeh Gregor wrote:
>
>> Another arg
16 matches
Mail list logo
