Quote:
|
Originally Posted by Gregory
does that imply that if we find problems in 13302 that have been solved in later releases that we should tell you about them as I did in this thread?
|
Yes, indeed--thank you.
Even better would be if you can figure out which Nightly first fixed the problem (so we can narrow down our search for the actual change that fixed it).
Quote:
|
Originally Posted by Gregory
Quote:
|
Originally Posted by Len Case
but some of our customizations will have to be rewritten to move away from the Cocoa controls
|
confused: isn't Apple 'softly' advocating developers to use Cocoa for the sake of 'easier' universal builds? |
The issue is that WebKit no longer uses cocoa to draw internal form elements on a webpage. This is because Cocoa controls (buttons, text fields, etc.) were never designed to be used inside a web page and don't correctly handle floating divs, etc. also they don't handle all the drawing methods that CSS can specify (like border colors, etc.). This is good for standards compliance but bad for our customizations since we have to redo them to work with the new implementation.
That said, WebKit is a Cocoa framework so using WebKit *is* using Cocoa.