You could use a bit of JavaScript to detect on page load whether the URL has a hash (#) and then force the jump to there (something like http://www.brandspankingnew.net/specials/anchorjump/anchorjump_01.html). That might sort the Safari "won't jump to anchors on page load" problem. However it sounds like your user is relaxed about it, so it probably isn't worth the effort :0)
Chris -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Kevin Futter Sent: 28 March 2006 06:37 To: [email protected] Subject: Re: [WSG] Safari and table row id On 28/3/06 4:39 PM, "Andreas Boehmer [Addictive Media]" <[EMAIL PROTECTED]> wrote: >> -----Original Message----- >> From: [email protected] >> [mailto:[EMAIL PROTECTED] On Behalf Of Kevin Futter >> Sent: Tuesday, 28 March 2006 2:16 PM >> To: [email protected] >> Subject: [WSG] Safari and table row id >> >> Not sure how on-topic this is, but I'll give it a shot. I've >> developed an internal page (sorry, no link to give you) that pulls IP >> addresses out of a database and allows you to 'manage' them (edit, >> change, add notes etc). Once edited (on a separate edit page), I send >> the user back to the main page, which is meant to jump down to the >> table row they've just finished editing. >> Works OK everywhere I need it to except Safari, which seems to have >> an issue scrolling to an anchor within a table - it just stops at the >> top of the table. I'm using URLs like this: (...)/index.php#ip_40 to >> achieve this, where #ip_40 is the ID of the tr element in question. > > Hi Kevin, > > Samuel's suggestions sound like a good starting point. Not sure if > Safari has got difficulties with jumping to IDs. Perhaps you could try > creating the old fashioned <a name="ip_40"></a> anchor to see if that works? Tried that, and unfortunately it didn't work (although I only did a quick test by wrapping the tr in an a element - probably should try just the IP address inside the td). I also did a quick test using <p id="whatever">text</p> and going to url/index.php#whatever, and that actually worked, as long as it was outside the table. I'd say a Safari bug is the culprit, as it definitely works elsewhere. Anyway, thanks for all the responses. It's not critical as the one Safari user on our team doesn't seem to mind if it doesn't work properly. How I wish all my clients were that accommodating! -- Kevin Futter Webmaster, St. Bernard's College http://www.sbc.melb.catholic.edu.au/ ****************************************************** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help ****************************************************** ****************************************************** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help ******************************************************
