[EMAIL PROTECTED] wrote:
Barney,
I am confused by this - did you download WebKit, or some other utility?
If it was just WebKit, then at least you know that the bug will be gone
from a future version of Safari !
Mike
Yes, I did... And that is kind of a guilty, comforting thought;
hopefully by the time the project goes live, everybody using Safari will
have updated to a version that doesn't suffer the same problem!
However I'm not sure that's how it works... All Apple-made Mac OS html
readers use WebKit, and WebKit is open source - are the two instances of
WebKit in that sentence referring to exactly the same thing? For one,
webkit.org doesn't mention the word 'Apple', nor does it have much in
the way of documentation re:release dates. So I'm a little confused.
If this is the bona fide, official, endorsed shape of things to come,
we're all very lucky people!
In the meantime, Safari appears to be completely vanilla, in that it has
no extensions, and is utterly opaque. Are these assumptions correct? Or
is there some way I can find out what the current release of Safari is
reading, other than staring at the source code and the final render?
I do know that generally it treats the styling of forms with disdain
(plus I'm using javascript on them for display purposes, oo-er). Is
there any other significant 'bug' I should know about?
Can't divulge urls sadly, but it's a question (as far as I can see) of
measurements mis-calculations inside a form element. I know that's vague
as anything... ???
Regards,
Barney
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
