Since browsers implemented a different fillRule API than what the spec
had, I've updated the spec to better match implementations.
Because the browsers just went ahead and implemented this, I didn't end up
responding to the feedback on this topic, since the reply to all that
feedback is "the s
On Thu, Apr 25, 2013 at 5:15 PM, Bjoern Hoehrmann wrote:
> * Glenn Maynard wrote:
>>This seems a bit heavy-handed. For these use cases, it doesn't seem like
>>you need to delay the whole onload event, which would have tons of
>>side-effects on the page. You could just tell the browser that you'r
* Glenn Maynard wrote:
>This seems a bit heavy-handed. For these use cases, it doesn't seem like
>you need to delay the whole onload event, which would have tons of
>side-effects on the page. You could just tell the browser that you're
>still doing things, without it having other script-visible e
On Thu, Apr 25, 2013 at 12:17 PM, Boris Zbarsky wrote:
> On 4/25/13 3:10 PM, Christian Biesinger wrote:
>> Ah, I see. It's not entirely clear to me what ASK_FOR_BASELINE means
>> and what ascent is initialized to when it's not set to that value
>
>
> Basically in this case it means that the child
On 4/25/13 3:10 PM, Christian Biesinger wrote:
From the top of the content box? Maybe I'm using the term wrong - I
mean the border-box minus borders and padding, which is a slightly
different definition than you used above.
That's the content box, yes.
Ah, I see. It's not entirely clear to m
On Thu, Apr 25, 2013 at 11:05 AM, Boris Zbarsky wrote:
> On 4/25/13 1:58 PM, Christian Biesinger wrote:
>>>
>>> Gecko puts the baseline of the button at the baseline of the button's
>>> text,
>>> and if the button is not auto-height the extra height is added (or
>>> removed)
>>> equally from above
On 4/25/13 1:58 PM, Christian Biesinger wrote:
Gecko puts the baseline of the button at the baseline of the button's text,
and if the button is not auto-height the extra height is added (or removed)
equally from above and below the text.
Hm, but I don't think that's completely correct, because
On Thu, Apr 25, 2013 at 10:48 AM, Boris Zbarsky wrote:
> On 4/25/13 1:43 PM, Christian Biesinger wrote:
>>
>> Where should the button be positioned relative to the input field (or
>> if you prefer, the baseline of the block)?
>
>
> The question you are really asking is "where is the baseline of th
On 4/25/13 1:43 PM, Christian Biesinger wrote:
Where should the button be positioned relative to the input field (or
if you prefer, the baseline of the block)?
The question you are really asking is "where is the baseline of the
button?", right?
Chrome dev, IE and Opera
put the bottom of the
Hi,
I had to recently investigate issues with the alignment of empty
buttons, i.e. , and I noticed some browser
differences.
Specifically, take this testcase:
http://plexode.com/eval3/#s=aekVQXANJVQMbAx14Hz1PdQFcAYMbARIYUVkcAYYOfp8Zo6WFn6KkXphDVlVVUE+bnZ8aEawBsk8dEJaYmB11HwEdtLa4H8PNt08fA14A
Whe
10 matches
Mail list logo
