jump to new posts or a specific post misses the mark

[Bobitybob]

Advertisement (gone after registration)

4 hours ago, Graham (G4FUJ) said:

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.

This is my experience and may have been the consequence of the update as I only recall it happening for the past few weeks. 

My normal viewing habits are to go to unread content in followed threads using the 'New Followed Content' link.  On the new page generated, I click on the dot/star to go to the last/newest post in that thread.  Having browsed these threads, I mark the rest of the site read using the 'Mark site read' link before signing out.  I've used this process for the last couple of years without problem.

I use a Mac and an iPad with the latest versions of the OS.  The 'new/abnormal' behaviour is the same irrespective of which browser I use on either of these devices.  For completeness, I have tried the following browsers, Safari, DuckDuck Go and Brave, they all exhibit the same issue.

Hope that's helpful.

[Advertisement]

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

[LocalHero1953]

23 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

An example from this morning.

I received a notification (via the bell icon top right of the page) that someone liked my post #150. I clicked on the notification and found I was actually at post #148 (which I quote in my own post, but this may be a coincidence).

An oddity: looking at my post, I click on the text '#150' and I am taken to post #148. On that post, I click on the the text '#148' and I am taken exactly to post #148.

Something strange going on. 

[LocalHero1953]

A different example from just now:

A thread was flagged in my 'new content' feed as having new posts. I clicked on the line in the feed and was taken to the top of the relevant page, not the bottom where this solitary new post was - the 13th post on the page.

[pop]

28 minutes ago, LocalHero1953 said:

A different example from just now:

A thread was flagged in my 'new content' feed as having new posts. I clicked on the line in the feed and was taken to the top of the relevant page, not the bottom where this solitary new post was - the 13th post on the page.

There's a setting for that: https://www.l-camera-forum.com/settings/links/

[LocalHero1953]

50 minutes ago, pop said:

There's a setting for that: https://www.l-camera-forum.com/settings/links/

Thanks, but mine is already set to 'take me to the comments I haven't read'

[ianman]

2 hours ago, LocalHero1953 said:

I received a notification (via the bell icon top right of the page) that someone liked my post #150.

When I click on the link I just quoted the browser goes to somewhere between #146 and #147. The top of the window is level with the top of Gibbos red telephone.

iPad - Safari - latest OS

[ianman]

Advertisement (gone after registration)

@LUF Admin

Andreas,

I still think Paul's thought of the images loading after the rest of the content is causing the issue. I've just looked at the code and see this:

data-ratio="68.96" style="height:auto;" width="1092"

which means that - as hinted in my post #7 - the <img> tag has no defined height, it's a calculated height applied through inline CSS. Although this is a common method, I believe it is not the best. In fact the CSS ignores the html "width" attribute and can only get the correct height to allocate to the <img> container once the image has been downloaded. I believe this is what could be causing the issue.

The solution seems simple though. You have the aspect ratio and the fixed desired width. In the backend you could hence very easily include a correct and fixed data value for the "height" attribute.
In this example 1092 * 0.6896 --> height="753"

Edited October 18, 2022 by ianman

[LUF Admin]

3 hours ago, ianman said:

the <img> tag has no defined height, it's a calculated height applied through inline CSS. Although this is a common method, I believe it is not the best. In fact the CSS ignores the html "width" attribute and can only get the correct height to allocate to the <img> container once the image has been downloaded. I believe this is what could be causing the issue.

@ianman Thanks for taking a deeper look. But things are a little bit more complex than calculating correct image dimensions.

If you visit the forum via other devices (iPad, iPhone, TV Screen, etc.) images will have different dimensions. Simply drag your browser window small and you'll see that embedded images change their dimensions too.

I agree that fixed dimensions have massive benefits (faster display of a page, no layout changes while loading thus better SEO ranking). But the forum has to work on a lot of different devices – so this is not an option.

The incorrect jump marks are more related to another feature: Lazy loading. If you go to a forum page only images will load that are visible. If you scroll down, more images are loaded when you get to them. This helps a lot with loading performance but has negative results if you don't scroll but jump to a location further down on a page. Suddenly all images need to be loaded and shift the page downwards. This can result in the issue we are discussing here.

Please believe me: This is a complicated issue which isn't solved with a single stroke.

Same goes with your first post:

On 10/2/2022 at 5:18 PM, ianman said:

Firstly an anchor tag is usually used the other way round. Any hyperlink in HTML is contained within an anchor tag.

[…]

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.

Same here: This isn't the problem and what you suggest isn't a solution. <a …> tags come in two varieties: Links with a target link (href option) and anchors with an id option. This is the jump mark where the links we are talking about should go to. They don't need any content.

[LocalHero1953]

That explains why I couldn't reproduce the issue with old notifications - because the whole page with all the images was cached locally.

[ianman]

41 minutes ago, LUF Admin said:

The incorrect jump marks are more related to another feature: Lazy loading. If you go to a forum page only images will load that are visible. If you scroll down, more images are loaded when you get to them. This helps a lot with loading performance but has negative results if you don't scroll but jump to a location further down on a page. Suddenly all images need to be loaded and shift the page downwards.

Lazy loading support the fact that the <img> has no height until the image is loaded. Right now having the width set at 1092 and height at auto will result in the <img> container having no height when the page is rendered. Having the backend enter the correct height will result in the container having the right dimensions, even if the source image is not yet loaded.

I’ve not had a look at the code for responsiveness but having the image dimension attribute fixed does not seem to affect the responsiveness. Indeed the width of the displayed images adapts correctly to the screen when a window is changed size even though the width attribute has an invariable value. I tested this using the chrome developer tools without any issues in the laptop browser or in the simulated devices.

Anyway, I just wanted to make sure my comment was understandable, as I wrote previously, I know I’m not always very clear  … just trying to help  

[ianman]

3 minutes ago, LocalHero1953 said:

That explains why I couldn't reproduce the issue with old notifications - because the whole page with all the images was cached locally.

On my iPad I have the same problem if I visit a link twice in succession. I’m not sure if I can check if the images are cached.

[Bart D]

I have the impression things were working better this evening.

Some links, unread posts by clicking on the star / bullet in front of the thread tile or from a notification on a reaction, got precisely to the proper place in the thread.
I even thought it was fixed.

Then I followed some that were again way off or just a little.

[Gibbo]

I thought I was only seeing this problem in safari because I hadn’t noticed it in iOS. However I have now seen a few occasions, on my iPhone, when clicking on the dot or star, nothing happens. You don’t get directed anywhere but the dot/star is no longer highlighted. So you have no idea where to start looking for the most recent post. The only option is to go to the end of the thread then scroll back to a post you recognise. 

[Bobitybob]

Any news on this?  It is still sending me to random posts on the last page viewed.

[Gibbo]

Andreas did say that there isn’t a quick fix for this. 

[Gibbo]

Just updating for the New Year.

This is still a problem.

[evikne]

On 10/18/2022 at 5:07 PM, LUF Admin said:

The incorrect jump marks are more related to another feature: Lazy loading. If you go to a forum page only images will load that are visible. If you scroll down, more images are loaded when you get to them. This helps a lot with loading performance but has negative results if you don't scroll but jump to a location further down on a page. Suddenly all images need to be loaded and shift the page downwards. This can result in the issue we are discussing here.

Please believe me: This is a complicated issue which isn't solved with a single stroke.

I have a little idea for the notification list (the bell icon): When we hover over a link there, the relevant posts could appear in a small pop-up window. This is sufficient to see which post someone has liked, and it can save us a lot of time and effort in finding the right posts. A click can work as before and take us to the thread.

This is probably not as relevant in the forum overview or in the activity streams, where we also want to read the following posts, but in the notification list this is usually not necessary.