Stream: IG creation
Topic: Transitions between IG pages
Lloyd McKenzie (May 03 2021 at 16:26):
Last summer, we merged in a template change from @Eric Haas that 'smoothed' transitions by providing a fade-in/fade-out between pages. However, this also means that a page doesn't render until everything for the page has been received and processed. This delay can be significant if you're on a slow connection, if there is 'code rendering' that needs to happen (particularly noticeable for RDF), etc.
Personally, I don't find the jitter that this smoothing was intended to address. (To see an example, just load http://hl7.org/fhir - you'll see the heading shifts right a few hundred milliseconds after it first opens.) I find the delay to display injected by the fade-in/fade-out process much more problematic. I would therefore like to roll-back the 'smoothing' process. However, I agreed with Eric that I'd raise the issue here first to get a broader consensus on the change.
Oliver Egger (May 03 2021 at 18:31):
+1 for a roll-back
Eric Haas (May 03 2021 at 20:07):
+1 for actually fixing the annoying left to right shift off the header with each page transition. My fix only partially smoothed it out but it is still present. I don't know what the solution is but the fade out and in is actually not long enough.
Jose Costa Teixeira (May 03 2021 at 20:37):
+1 for rolling it back. the annoying jitter seems caused by a single css setting
Jose Costa Teixeira (May 03 2021 at 20:37):
jitter / flickering / .... the annoying shift in the heading and body
Jose Costa Teixeira (May 03 2021 at 20:45):
does anyone (else) have an IG with the issue to test a fix?
Lloyd McKenzie (May 03 2021 at 21:01):
If I roll it back, everyone will soon enough :)
Lloyd McKenzie (May 03 2021 at 21:01):
I'm certainly fine with fixing whatever's creating the shift if it can be done without introducing any sort of delay.
Jose Costa Teixeira (May 03 2021 at 21:04):
i tested it locally but i don't trust anything that works on my machine.
Jose Costa Teixeira (May 03 2021 at 21:05):
that's why I'd want someone else to test it
Eric Haas (May 03 2021 at 21:48):
this is browser dependent too. but is easy to compare before and after by going to an early version of US Core and compare with the latest. There is really very little difference in some Google based browsers.
Jose Costa Teixeira (May 03 2021 at 22:55):
the issue i found was not browser specific
Jose Costa Teixeira (May 03 2021 at 22:57):
@Eric Haas if you want to test it please, it's easy: just delete all the contents in the bootstrap.css (leave the file so that it's not overwritten by the base template)
Eric Haas (May 04 2021 at 15:16):
After removing the fade in and out, please check and see if it is indeed the culprit. I suspect the syntax highlighter is the real culprit here.
Eric Haas (May 04 2021 at 15:18):
@Jose Costa Teixeira we cannot simply remove the bootstrap.css if that is what you are suggesting. it is for instance responsible for responsive behavior.
Jose Costa Teixeira (May 04 2021 at 15:19):
@Eric Haas check the template now
Jose Costa Teixeira (May 04 2021 at 15:20):
the fade in and out was removeed, the flicker was gone (on my machine), one of the bootstrap.css is gone
Eric Haas (May 04 2021 at 16:09):
responsive stuff seems to be working (except for code blocks , but I don't know if they ever did and I can live with that for now )
Last updated: Apr 12 2022 at 19:14 UTC
