Re: Continuing Improvements to Web Kit and Dashboard

I'm glad Matt is bringing WebKit testing up again as I had posted a query over a month ago (Dec. 23) and never received a response.

Here it is again:

-----

I've noted a problem with the rendering of a "glassbutton" on the back of my widget when run in WebKit's Safari.

There is no problem under OS X 10.4.8 when the widget is run in Safari nor when run in the Dashboard.

The widget uses Apple "AppleButton.js" found in "AppleClasses" to produce the "Done" button on its back side.

The same problem occurs in Apple's sample code "Fader" widget, which likewise uses "AppleButton.js" from "AppleClasses" for its "Done" button.

Here is an ASCII art representation of the problem (view in a monospaced font!):

 __              __

|  | __________ |  |

|  ||          ||  |

|__||   DONE   ||__|

    |__________|

The button is built up from three parts: a left and right side and a center. As you can see above, the center portion is vertically displaced from the 2 sides when the widget is viewed under WebKit.

The js code that Apple's Fader sample widget uses is here:

http://developer.apple.com/samplecode/Fader/listing2.html

I did a quick search of the WebKit Bugzilla site but could not find this reported. (However, I'm not very familiar with using Bugzilla, so I may have missed a report of this problem.)

Can someone shed some light on this?

Thanks.

-----

By the way, Apple's "Fader" is certainly not the only widget that shows this problematic Done button layout. Apple's Weather also shows this problem as well as others...

Cheers,

Jim

On Jan 31, 2007, at 2:02 PM, Matt Drance wrote:

Date: Wed, 31 Jan 2007 10:37:34 -0800

From: Matt Drance <email@hidden>

Subject: Re: Continuing Improvements to Web Kit and Dashboard

To: Johnny Storm <email@hidden>

Cc: email@hidden

Message-ID: <email@hidden">email@hidden>

Content-Type: text/plain; charset="us-ascii"

The widget object is unique to Dashboard, so unfortunately it cannot

be enabled in Safari (or nightly Safari).  At the same time, that

means the nightly Web Kit builds wouldn't affect the widget object

anyway.  The goal here is to test the layout content (HTML, CSS, JS,

DOM) that is common to both Safari and Dashboard.  You should be able

to examine the front and back divs of your widget without a problem.

-----------------------------------------------

Matt Drance

Sharing Technologies Evangelist

Worldwide Developer Relations

email@hidden