Hi all,
If the font size is not specified in the HTML page, what is the default one
used by webkit?
is there any way to dynamically set it? ( a .rc file for example)
regards.
haithem
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
Hello ,
It's my first time posting here :) Thanks for the great work that you guys
have been doing.
I just have a simple idea for the box-shadow CSS3 property:
I would like to suggest that a feather or blur value be added to the
property. This will allow designers to create soft shadows for
On Jul 19, 2009, at 8:35 AM, Raymond Irving wrote:
Hello ,
It's my first time posting here :) Thanks for the great work that
you guys have been doing.
I just have a simple idea for the box-shadow CSS3 property:
This kind of suggestion is best sent to the www-style list if you're
Hi Simon,
My bad I missed the third parameter. Thanks for the feedback.
I have a look at it.
--- On Sun, 7/19/09, Simon Fraser simon.fra...@apple.com wrote:
From: Simon Fraser simon.fra...@apple.com
Subject: Re: [webkit-dev] Ideas for Box-shadow - CSS3
To: Raymond Irving xwis...@yahoo.com
You should test the same thing with window.onload. If I recall
correctly, you'll see similar inoperability.
Adam
On Sun, Jul 19, 2009 at 9:29 AM, Drew Wilsonatwil...@google.com wrote:
I was writing a new worker unit test and I noticed that all of our unit
tests set event handlers in worker
Yes, it happens with window.onload() too (I didn't mean to imply that it was
a worker-only issue).
This seems like precisely the type of inoperability that the HTML5 spec
should address, but I figured I should get some input here before bringing
it up there.
-atw
On Sun, Jul 19, 2009 at 10:31
I think we should do what Firefox does in the window.onload case. :)
I'm not familiar with the history through. Is there some particular
reason we have our current behavior?
Adam
On Sun, Jul 19, 2009 at 10:56 AM, Drew Wilsonatwil...@google.com wrote:
Yes, it happens with window.onload() too
On Jul 19, 2009, at 11:10 AM, Adam Barth wrote:
I think we should do what Firefox does in the window.onload case. :)
I'm not familiar with the history through. Is there some particular
reason we have our current behavior?
The current behavior is an accident of implementation, but I think
you could have a look at WebKit/your working
port/WebCoreSupport/EditorClientXXX.cpp :
void EditorClientXXX::setInputMethodState(bool active)
{
... code could come here ...
}
On Sat, Jul 18, 2009 at 7:10 AM, Nikolas
Zimmermannzimmerm...@physik.rwth-aachen.de wrote:
Am 18.07.2009 um 13:02
9 matches
Mail list logo
