Comments: Safari Response: bradchoate.com

Dave, it looks like Brad is using a transparant PNG file as a background in that CSS definition:

div.nicetitle {
position: absolute;
padding: 4px;
top: 0px;
left: 0px;
color: white;
font-size: 13px;
font-family: Verdana, Helvetica, Arial, sans-serif;
width: 25em;
font-weight: bold;
background: url(/images/ntbg.png);

/* Mozilla proprietary */
-moz-border-radius: 12px;
}
div.nicetitle p {
margin: 0; padding: 0 3px;
}
div.nicetitle p.destination {
font-size: 9px;
text-align: left;
padding-top: 3px;
}

Posted by Jack at February 14, 2003 1:01 AM

Here is an excellent article on the subject of PNG including opacity.

http://www.alistapart.com/stories/pngopacity/

Posted by Jack at February 14, 2003 1:12 AM

Ah, I see. I totally forgot that we supported that in Safari. ROFL.

Posted by David HYatt at February 14, 2003 1:22 AM

I know we all like our web sites to be real REAL pretty, but please don't expend too much time on this kind of goofy stuff.

If I can be the googleplex+1 person to make a suggestion for Safari...

When one considers that a notable percentage of OS X users (which is quickly becoming synonymous with Safari users), the need to run Safari through an intense gauntlet of browser-based development tools should be an essential part of the beta process. A significant one that comes to mind is Webmin, which is wrought with bugs and weird behavior. On the other end of browser-based adminstration tools is the oft-employed hosting admin tool, CPanel hangs randomly on submissions.

One of the biggest development problems has finally been fixed, being the problems that the previous beta had with resolving localhost correctly (THANK YOU).

Keep up the good work David!

Posted by Brian Douglas at February 14, 2003 1:49 AM

I work on WebCore. It's my job to make Safari work with "this kind of goofy stuff." :) There are other people on the Safari team who work in other areas (e.g., JavaScriptCore, WebFoundation, WebKit, the browser GUI, etc.).

Posted by David Hyatt at February 14, 2003 1:53 AM

Would a problem that affects my own blog's formatted links be also fixed with the new inline box model code? For some reason a:hover does not change the background of links that are in or tags.

Posted by Orestes at February 14, 2003 4:29 AM

Oops. That should have been <b> or <i> tags. Next time I will click on "preview" before I click on post.

I have sent in a bug report on this a:hover background issue.

Posted by Orestes at February 14, 2003 4:32 AM

I can't take the credit for this. It's a little gizmo I found here:
http://www.kryogenix.org/code/browser/nicetitle/

Thanks for fixing the background CSS thing though! Great job all around on Safari, btw.

So when can we expect a Windows version? I mean Apple does maintain Quicktime for Windows, so it's not so strange a concept, right?

Posted by Brad Choate at February 14, 2003 4:37 AM

I am really hankering after this inline box model now. ;)

Posted by d at February 14, 2003 9:56 AM

Interesting item of note, MSIE for windows doesn't properly support PNG transparency. I find this very funny since IE for Mac does!

Kudos on that, it's let me do some REALLY cool stuff.

Posted by Chiper at February 14, 2003 12:04 PM

Dave

I am tickled with the improvements of the new version of Safari -- I am still learning css, but have tried to push myself in its creative use: www.riverchurch.net uses some stuff I learned at Eric Meyers site and it is being displayed right/mostly right as of v60. Yeah! Good work!

I have a site (and did send a bug report) though that displayed mostly ok with v51, but now crashes Safari v60 (www.MichiganUB.com/index2.html). Not sure why - upgraded the page yesterday so that it validates at w3c.org, but still it is crashing Safari v60. Seems to be tied to the meta statement and link statement of the stylesheet. But only with my pages using css2 positioning (I have been using LayoutMaster and StyleMaster from WestCiv.com). Added the same statements into another page without the position stuff - and no problem. I am having similar crashes on the new Netscape's Developers Edge Design (and again, v51 handles it without crashing - though not perfectly).

feedback fwiw - and it easily could be something I have done wrong -- feel free to point it out to me if it is.

Mike

Posted by Mike at February 14, 2003 2:00 PM

There's nothing wrong with the fancy title tips gizmo, but I prefer the default tootip behavior we have in Mozilla and IE (Safari not in v60).

Posted by Fabricio Zuardi at February 16, 2003 11:15 AM

Maybe this is unrelated, but how come popup windows opened with javascript with scrollbars=no, still leave room for the scrollbars (i.e. they pad the size of popup window horizontally and vertically by around 20 pixels)? I can't find another browser that behaves this way. I hope this is not what's called an 'interface issue' and therefore irrelevant here, but it is the only remaining issue keeping me in IE.

Posted by Paul at February 19, 2003 2:56 PM

Hi,

Could someone post this where it might get noticed, thanks : )

I submitted a bug report on my friend's Mac. When the new version cam out I read that all the CSS bugs were fixed : |

I still notice 2 bugs in Safari:

The vertical spacing in tables equally divided. Perhaps vertical height in tables isn't supported.

Backgrounds do not seem to extend far enough. I am not sure why. It's a tricked-out page but it should work.

These browsers display the page correctly:

* Mozilla 1, 1.1, 1.2
* Phoenix .5
* Netscape Navigator® 6.2
* Chimera® .5
* Opera® 6.01
* Microsoft Internet Explorer® 5.5

Site: http://www.genderrain.com/

I wan't to add Safari to the list : )

[It's also a shame that most browsers do not support proper CSS table parameters. I gave up trying on including them in CSS and included them in the table tags.]

Thanks,
BrendaEM

Posted by BrendaEM at February 19, 2003 11:12 PM

The world is a beautiful book for those who can read it.

Posted by Friedman Joseph at January 25, 2004 7:10 AM

i'll just wait

Posted by allegiance healthcare at February 13, 2004 8:34 PM
Post a comment