Lissa Guillet System Administrator |
Steve Geddes |
Sorry, Lissa. I knew that was useful - don't know why I omitted it.
Unfortunately, here at work I'm struggling to recreate the problem! When I made my first post, I thought it was universally true on the product pages . Looks like not.
I know this page was problematic on my Ipad. Most of my avatar and the first half of the post on that page was obscured.
Here's one which is still obscured. (I can't see posts 1,2 or most of 3).
I'm using Firefox Qantum (?) 59.0.2 64 bit.
Joana |
My post of March 27th should be the sixth on the page; you can see that the post above mine has the avatar half-obscured and none of the text visible.
I'm using Chrome 65.0.3325.181 in Windows 10.
Franz Lunzer |
Here's a screenshot, hope that helps
Windows 7 (work) using Google Chrome V65.0.3325.181
CrystalSeas |
This page is not loading the discussion section correctly.
Both the top of the section and the bottom of the section are missing.
The top cuts off with only a few mm of the search button visible.
At the bottom, you have to click each posting date to see the next post.
http://paizo.com/products/btpy9tdi/discuss?Wayfinder-17#16
BenS |
Steve, can you see a cropped top of Product Discussion...Nidal, Land of Shadows? I think I recognize the avatar of the poster as Fallen Dabus (working from memory), but I see only the bottom half. I'm just curious since you said on my other listed page you didn't see the same cropping issue I had. And you appear to be using Safari as well.
Steve Geddes |
Here's another example. This is not showing the first five and a half posts on Firefox.
Tech team, can I ask if it's useful to continue posting every instance (there's quite a lot of them) or did you just need a few examples?
Steve Geddes |
Steve, can you see a cropped top of Product Discussion...Nidal, Land of Shadows? I think I recognize the avatar of the poster as Fallen Dabus (working from memory), but I see only the bottom half. I'm just curious since you said on my other listed page you didn't see the same cropping issue I had. And you appear to be using Safari as well.
Most of the time I use Firefox. Occasionally, I browse the product pages on Safari, but not often.
The Nidal page shows up fine for me on Firefox (I'll look when I get home on Safari).
Steve Geddes |
BenS |
Papa-DRB |
I am seeing the "cropping" of the first (few?) posts on the page in this thread:
http://paizo.com/products/btpy9i3d/discuss?Legendary-Planet-Players-Guide#2 3
And to add a twist to the issue, the display does not start at the last post, but way up the page to where I last posted in the thread.
Windows 7, Home Premium, 64 bit
Firefox Quantum, 59.0.2, 64 bit
-- david
Terminalmancer |
2 people marked this as a favorite. |
I have been able to reproduce the error by visiting
http://paizo.com/products/btpy9y26/discuss&page=4?Pathfinder-Adventure- Path-133-Secrets-of-Roderics-Cove#189
I haven't had much time to play with it but removing position:relative from the div class="tabs" and then re-adding it in developer tools fixes the position. It might be that the comments are being loaded in and positioned before the height of the item box is known?
Of course, as I'm testing this, I found another failure mode. Performing a hard reload shows the first post positioned correctly. The height of div class="post" is correct. But the height of div class="tab-content" is all of 352 pixels high, concealing the post content.
When I'm using cached files, though, I don't see the issue.
This might be something you need to inject artificial latency to see and debug. I'll see if I can get anything more concrete.
Terminalmancer |
5 people marked this as a favorite. |
Looks like the primary culprit is the interaction between the height of the div class="tabs" and the absolute positioning of the divs class="tab-content".
HTML/CSS-wise, the absolutely positioned content doesn't cause the parent elements to resize to fit. Removing position:absolute fixes the issue.
I don't want to go digging through your JS, but I'm guessing you're doing some dynamic assignment of element height before the content is done loading?
Hope some of that helps, at least.
Terminalmancer |
Hah, thanks Steve.
----
On another note, things are functioning much better now! And that is certainly, er, one way to solve the problem. :o)
It does create the issue Steve mentions, where anchor links to specific posts resolve before the content is done loading. I think you might need to rely on JS to solve this one--since the DOM is officially loaded before the page pulls in all the comments and the resize script resizes the containing element to match.
Erik Keith Software Test Engineer |
1 person marked this as a favorite. |
Hey everyone, we tried to get this resolved with a small release we did yesterday aimed at QoL and bug fixes. The thread cropping issue is still around, but I think we identified where things were going wrong. We're going to hold off on doing another attempt to resolve it likely until after PaizoCon, but it is on our radar.
BenS |
1 person marked this as a favorite. |
Hey everyone, we tried to get this resolved with a small release we did yesterday aimed at QoL and bug fixes. The thread cropping issue is still around, but I think we identified where things were going wrong. We're going to hold off on doing another attempt to resolve it likely until after PaizoCon, but it is on our radar.
I appreciate the timeline and active response a lot. The issue is annoying but I'm glad it's on the radar at least.
BenS |
Erik Keith wrote:Hey everyone, we tried to get this resolved with a small release we did yesterday aimed at QoL and bug fixes. The thread cropping issue is still around, but I think we identified where things were going wrong. We're going to hold off on doing another attempt to resolve it likely until after PaizoCon, but it is on our radar.I appreciate the timeline and active response a lot. The issue is annoying but I'm glad it's on the radar at least.
Bump b/c it's still happening.
Joana |
1 person marked this as a favorite. |
Not only is it still happening, but the threads it's happening on (i.e., this one) have another weird thing going on: When you click on the most recent post or (x new), the page loads at the correct post but then immediately "bounces" to the top of the page.
Chris Lambertz Web Product Manager |