Safari - couple of questions 1

[1DMF]

hello,

1. what are the access keys, i've tried all combinations, nothing works.

2. why is my menu dropping off, FF, IE , Opera, etc.. all are fine except Safari, what is it doing that the others don't?

http://www.justlifecover.co.uk

you'll notice the last menu option has fallen off and is on a new line.

Thanks
1DMF.

"In complete darkness we are all the same, only our knowledge and wisdom separates us, don't let your eyes deceive you."

"If a shortcut was meant to be easy, it wouldn't be a shortcut, it would be the way!

 

[BillyRayPreachersSon]

On a Mac, running Safari 3, it's "Ctrl" + the key.

Hope this helps,
Dan



Coedit Limited - Delivering standards compliant, accessible web solutions

[tt]Dan's Page [blue]@[/blue] Code Couch

http://www.codecouch.com/dan/

[/tt]

 

[monksnake]

On question no 1, what version of Safari do you have??

From what I've read only version 1.3.2 and higher support accesskeys, that is done with cntl + key instead of alt + key.



<.

 

[1DMF]

sorry - I wasn't clear ws I , i've just installed Safari eta 3 for windows , though I've been told it is doing it on a Mac also in safari , but not FF for Mac or IE for Mac

"In complete darkness we are all the same, only our knowledge and wisdom separates us, don't let your eyes deceive you."

"If a shortcut was meant to be easy, it wouldn't be a shortcut, it would be the way!

 

[1DMF]

Well if I change the padding on the last element by 15px it looks fine in safari but it's too small in every other browser.

It seem all the fonts and padding are all inflated in Safari, is this a know problem?

Every other browser I've tried looks fine, it's just safari with the problem, am I to assume it's a safari issue?

is there a way of writing CSS just for safari , any holy hacks someone could enlighten me with please.

"In complete darkness we are all the same, only our knowledge and wisdom separates us, don't let your eyes deceive you."

"If a shortcut was meant to be easy, it wouldn't be a shortcut, it would be the way!

 

[BabyJeffy]

You need look no further than the FAQ section...

faq215-6624

Cheers,
Jeff


[tt]Jeff's Page [!]@[/!] Code Couch

http://www.codecouch.com/jeff/blog/

http://www.coedit.co.uk/

[/tt]

Make sure your web page and css validates properly against the doctype you have chosen - before you attempt to debug a problem!

FAQ216-6094

 

[BillyRayPreachersSon]

I'd have thought that Safari in Windows shouldn't really suffer from that problem... How queer!

Dan



Coedit Limited - Delivering standards compliant, accessible web solutions

[tt]Dan's Page [blue]@[/blue] Code Couch

http://www.codecouch.com/dan/

[/tt]

 

[monksnake]

How queer!

....I'm mature.

<.

 

[1DMF]

now now Monksnake, pick yourself up of the floor, rolling around like a school girl isn't helping ;-)

also isn't 'queer' non-PC these days, not that I know anything about being PC

Thanks Jeff, only I loath to use inline / html CSS , I use a single external CSS and was hoping there might be a holy hack such as the IE6 '* html element'.

You know I never understood you guys when you used to be so peed off at browsers (no browser names mentioned, to protect the innocent), until I started doing things properly and trying to code to the standards, then it all becomes horribly clear.

In the end I simply made up two classes styling all the menu buttons a single fixed width except the end one and gave that it's required fixed width.

It's not quite the desired look / design i wanted, but because of the font size problem, it seemed to effect padding so had to remove the padding and apply the width.

Now everything looks fine no matter what browser I use.

If Mac is trying to win friends on Windows, they are doing a poor job so far!

"In complete darkness we are all the same, only our knowledge and wisdom separates us, don't let your eyes deceive you."

"If a shortcut was meant to be easy, it wouldn't be a shortcut, it would be the way!

 

[BabyJeffy]

I've been reading some online posts by Apple observers that indicate this is the first push for Apple to go head-to-head and aim for a Safari vs IE browser war -- effectively pushing the other browsers to the background and trying to get people to use Safari (in the same way they got them to use iTunes I guess).

I always thought they had released the Windows version of Safari so that they had a development platform for iPhone developers in Windows. I think I was only partially right on this... and maybe this is indeed Apple's foray into the next generation browser war... and if it is, they do indeed have along way to go

Cheers,
Jeff


[tt]Jeff's Page [!]@[/!] Code Couch

http://www.codecouch.com/jeff/blog/

http://www.coedit.co.uk/

[/tt]

Make sure your web page and css validates properly against the doctype you have chosen - before you attempt to debug a problem!

FAQ216-6094

 

[1DMF]

I'd have thought that Safari in Windows shouldn't really suffer from that problem

then again, at least the fact it behaved like safari on a Mac, it enabled me to see the Mac reported problem and fix it, so I guess I mustn't grumble really

"In complete darkness we are all the same, only our knowledge and wisdom separates us, don't let your eyes deceive you."

"If a shortcut was meant to be easy, it wouldn't be a shortcut, it would be the way!

 

[ChrisHunt]

I'd have thought that Safari in Windows shouldn't really suffer from that problem

I've read that Safari/win uses the same text rendering method as the Mac does (as opposed to using ClearType). Presumably the notional 72/96ppi issue comes along as a bonus.


-- Chris Hunt
Webmaster & Tragedian
Extra Connections Ltd

 

[Foamcow]

The 72/96ppi thing is historical.
Apple opted for 72ppi presumably due to it's early adoption of PostScript. Or possibly because of the small screen on those early Macs?

I thought the Mac version of Safari would use the Quartz(?) type rendering engine which is an OS thing so wouldn't be available to Windows users?

OS X type rendering is excellent.

<honk>*:O)</honk>

Tyres: Mine's a pint of the black stuff.
Mike: You can't drink a pint of Bovril.

 

[1DMF]

I thought the Mac version of Safari would use the Quartz(?) type rendering engine which is an OS thing so wouldn't be available to Windows users?

OS X type rendering is excellent.

but would that suggest Safari on Mac , Safari on OS X and Safari on Windows would all render differently?

it seemed they were all causing the same problem for me, so something must be the same across the board, that non of the other Windows browsers do?

also that FAQ link says this

Macs render text at a screen resolution of 72 pixels per inch (ppi) ... Windows renders type at a notional screen resolution of 96 ppi... the difference between 96 ppi and 72 ppi (24 pixels) makes the fonts on a Web page look 33 percent larger when viewed on a Windows machine.

But the problem was happening in safari on a Mac as well as safari in widnows, which indicates that the fonts ar bigger in safari and not OS related.

the fonts are bigger on a Mac not Windows, which was also the problem.

So which way round is it? and what is the culprit?





"In complete darkness we are all the same, only our knowledge and wisdom separates us, don't let your eyes deceive you."

"If a shortcut was meant to be easy, it wouldn't be a shortcut, it would be the way!