jump to new posts or a specific post misses the mark

[Bart D]

Advertisement (gone after registration)

You get delivered to somewhere in the vicinity of the intended post in the thread but never correctly anymore.

Since some days.

Mac, macOS 12.6, edge

 

Edited October 2, 2022 by Bart D
added system info

[evikne]

[Advertisement]

The Leica Q3 is available for pre-order at B&H Photo Video and Adorama

[pop]

It doesn't properly work with Firefox under Linux, either.

[LocalHero1953]

Happens to me with Chrome under macOS.

I'm guessing it is to do with the order in which the browser loads the page elements: it takes you to the right post on the page, then adds the page photos above and below, which shifts your landing point.

So it could be either the browser, or how the page is coded.

[ianman]

The link points to an anchor element with an id in the form of comment-xxxxxxx , where xxxxxxx is a number, I'n guessing the id of a record in the database.

The target page contains the anchor element with the corresponding id attribute. Here on the forum, the element in question has no content but is placed just above the element containing the actual content in the HTML flow.

Two things strike me being a bit strange:

Firstly an anchor tag is usually used the other way round. Any hyperlink in HTML is contained within an anchor tag. A very simple (and wouldn't work) form would look <a>like this</a>. In the browser it would be rendered in colour and underlined unless this style is overriden by CSS. Link can be made other ways but this is the bog standard method and there is no point in going into details.

So point 1 is why use an anchor element as the target for the link?

Second is the targeted anchor tag is empty, it has no content (it looks like this: <a id="comment-xxxxxxx"></a>). I'm guessing this is causing the issue because the tag has no role in defining the page layout.

As it happens, the subsequent element in the HTML flow is an <article> which has an ID attribute (id="elComment_xxxxxxx"). The article element is a page layout defining element so it would make more sense to point the initial link to #elComment_xxxxxxx or to get rid of the useless <a> element and change the ID of the <article > to comment-xxxxxxx.

 

[Bart D]

2 hours ago, ianman said:

The link points to an anchor element with an id in the form of comment-xxxxxxx , where xxxxxxx is a number, I'n guessing the id of a record in the database.

The target page contains the anchor element with the corresponding id attribute. Here on the forum, the element in question has no content but is placed just above the element containing the actual content in the HTML flow.

Two things strike me being a bit strange:

Firstly an anchor tag is usually used the other way round. Any hyperlink in HTML is contained within an anchor tag. A very simple (and wouldn't work) form would look <a>like this</a>. In the browser it would be rendered in colour and underlined unless this style is overriden by CSS. Link can be made other ways but this is the bog standard method and there is no point in going into details.

So point 1 is why use an anchor element as the target for the link?

Second is the targeted anchor tag is empty, it has no content (it looks like this: <a id="comment-xxxxxxx"></a>). I'm guessing this is causing the issue because the tag has no role in defining the page layout.

As it happens, the subsequent element in the HTML flow is an <article> which has an ID attribute (id="elComment_xxxxxxx"). The article element is a page layout defining element so it would make more sense to point the initial link to #elComment_xxxxxxx or to get rid of the useless <a> element and change the ID of the <article > to comment-xxxxxxx.

 

sounds complicated 😃

[ianman]

Advertisement (gone after registration)

3 hours ago, Bart D said:

sounds complicated 😃

It’s actually very simple but I’m rubbish at explaining things

However I just read Paul’s post too. That would make sense if the image containers had no defined dimensions Which is possible but I’m not in front of my laptop right now so I can’t check.

[Gibbo]

This bug is really quite an irritant!

[Bobitybob]

This still doesn’t appear to be working as it did, any chance of a fix?

[LocalHero1953]

+1

It is a real problem that when I get a notification that someone has reacted to one of my posts but I can't jump to it to find out which one it is. I jump to the middle of the thread with no idea how far away I am from the relevant post.

An update would be appreciated.

[Gibbo]

Has this been noticed by admin?

[Bart D]

16 hours ago, Gibbo said:

Has this been noticed by admin?

it's in the right forum, isn't it

[Graham (G4FUJ)]

Glad it's not just me.

Problem has been going on since an update last? week.  It's a trifle frustrating.

[ianman]

37 minutes ago, Graham (G4FUJ) said:

It's a trifle frustrating.

And there’s not much worse than a frustrated trifle!

To be honest I’ve been having this issue for a while but never mentioned it. It happens even in this thread where there are no images.

@LUF Admin have you seen this thread?

[Bobitybob]

Is there anybody there, or do I need to search for the ouija board!

[LUF Admin]

Back from my vacation, will look into this.

I made an update three weeks ago which – in my experienced – improved this function, but obviously you made other experiences…

Will check.

Can you give me some details?

• Where do you click the link?
• What is the exact target link?
• Where are you linked to?
• What browser are you using?

Andreas

[evikne]

I mentioned this bug in June, and tried to explain a bit how it behaved. See the link in post #2 in this thread.

I have experienced some minor changes in the way Safari behaves after the latest update, but it didn't solve the problem.

Edited October 17, 2022 by evikne

[ianman]

3 hours ago, LUF Admin said:

What is the exact target link?

Andreas, my description in post 5 gives some details on this.

Edited October 17, 2022 by ianman

[Graham (G4FUJ)]

Hi Andreas,

Answers sort of in reverse order.

Win 7, usually Google Chrome browser.

Click on little dot (or star  should I have already posed in a thread) to left of a thread title. 

Until fairly recently this would take me to the next unread post.  However, of late  this now goes to somewhere in the thread showing earlier posts already read. If a short thread, it might actually go to the bottom of the last page.

Hope that helps.

[Advertisement]

Hallo,

Look here: Interesting Leica gear

[LocalHero1953]

4 hours ago, LUF Admin said:

Back from my vacation, will look into this.

I made an update three weeks ago which – in my experienced – improved this function, but obviously you made other experiences…

Will check.

Can you give me some details?

• Where do you click the link?
• What is the exact target link?
• Where are you linked to?
• What browser are you using?

Andreas

My recollection is that the issue has been around for more than three weeks.

I normal click the link in the notifications section (the bell at the top of the page) where I have been told that someone has 'liked' one of my posts. The target this therefore in a thread which I am not normally already in.

Interestingly, I went back to the last half dozen notifications to see if I could reproduce it and answer your questions: every one found the correct post without error! (All the notifications, when new, had produced the error). I shall have to wait for a new notification before I can answer your questions.

I am using Chrome on a Macbook.