|
|
|
Use this tool to learn about websites, specifically the one you just entered. If you find some aspect of it inappropriate it is not our fault. If you are the owner of this website: yes we are a real search engine, we do have a real web crawler called FyberSpider and you can block it if you feel the urge.
We are in the process of updating this tool. Until we are done just use our search results to check the inclusion status of your site.
Surfin' Safari
This is just a sample of the content found on this website. Please visit the website to read the entire page. "Surfin' Safari Front Page - Technorati April 30, 2005 Safari and KHTML Posted at 9:26 PM KHTML developers respond to my posting of the WebCore Acid2 patches here and here . For what it's worth, the patches I posted are to WebCore , which consists of both KHTML and KWQ (our port of Qt). They are posted to illustrate all the WebCore bugs that had to be fixed in Safari to pass the Acid2 test. They are not solely KHTML patches. The antialiasing bug was in KWQ, and so doesn't even apply to KHTML. The better object element support necessarily involves KWQ as well, since the plugin code is (obviously) platform-specific. What do you think Apple could be doing better here? Comment or trackback. I'll read it all. comment (69) - April 27, 2005 Safari Passes the Acid2 Test (Updated) Posted at 10:25 PM Safari now passes the Acid2 test. There were two issues left that needed to be resolved. The first issue involved implementing a few enhancements to the object element. I needed to support fallback content when invalid MIME types were specified or when bad status codes were returned for HTTP requests (like 404). After fixing these bugs and a couple of other problems with intrinsic sizing of plugins, the eyes of the face showed up. The second issue involved improper antialiasing of the border corners. Antialiasing was enabled for the drawing of the corner polygons, and this resulted in a bleed-through of the background. Because the two corners were drawn separately, the antialiasing was actually incorrect, since it was disrupting the join of the corners by letting the background show. Here are the patches for all of the problems fixed in Safari to make the test pass. Fix parsing of the REL attribute on links. Disallow TABLE inside P in strict mode. Add support for min/max-width/height for positioned elements. Fix the rendering glitch that causes the" .... read entire page
|
|
|