Onscreen Appearance of LLORG
-
- x 7661
Re: Onscreen Appearance of LLORG
Thank you, one and all, for responding to my pleas for assistance. The problem with the onscreen appearance of the LLORG seems to have resolved itself. Perhaps the source was background updates in Chrome, afterall. Then again, perhaps it was a hardware issue that is destined to recur; I've bounced my computer off the floor a couple of times over the past year (although not lately) and it is possible that sophisticated, delicate, electronic devices such as my laptop eventually find a way of expressing their discontent with such rough treatment.
1 x
- Serpent
- Black Belt - 3rd Dan
- Posts: 3657
- Joined: Sat Jul 18, 2015 10:54 am
- Location: Moskova
- Languages: heritage
Russian (native); Belarusian, Polish
fluent or close: Finnish (certified C1), English; Portuguese, Spanish, German, Italian
learning: Croatian+, Ukrainian; Romanian, Galician; Danish, Swedish; Estonian
exploring: Latin, Karelian, Catalan, Dutch, Czech, Latvian - x 5181
- Contact:
Re: Onscreen Appearance of LLORG
Sometimes my mum's computer problems resolve themselves mysteriously as soon as I appear
But seriously, no, such a specific problem can't be due to hardware.
They always know where it hurts mostSpeakeasy wrote:Then again, perhaps it was a hardware issue that is destined to recur; I've bounced my computer off the floor a couple of times over the past year (although not lately) and it is possible that sophisticated, delicate, electronic devices such as my laptop eventually find a way of expressing their discontent with such rough treatment.
But seriously, no, such a specific problem can't be due to hardware.
0 x
- rdearman
- Site Admin
- Posts: 7259
- Joined: Thu May 14, 2015 4:18 pm
- Location: United Kingdom
- Languages: English (N)
- Language Log: viewtopic.php?f=15&t=1836
- x 23307
- Contact:
Re: Onscreen Appearance of LLORG
The thing you are describing is most often caused by something called CSS, or cascading style sheets. When a webpage loads does the following steps.
At any point in the above something can go wrong. Also each browser has their own version of a "render engine" which is used to parse all the CSS, Javascript, HTML, etc.. Because each browser is different things which work in one browser may not work in another, or even a different version of the same browser. However, browsers are updated all the time, along with the render engine it uses. Although Chrome is very popular, it's render engine Blink isn't the best IMHO, I think the Geko engine used by Firefox is probably more strict regarding standards and rendering implementation.
You can try downloading Firefox here: https://www.mozilla.org/en-GB/firefox/new/ and see if it solves your problems.
Since your the only person experiencing the issue we can safely assume the problem is local to your PC. So, there really isn't anything we can do for you from here.
EDIT: Oh, and firefox doesn't send your information to the Google Mothership.
- When a connection is open, the HTTP request is sent to the host server from your laptop.
- The host forwards the request to the server software (most often Apache) configured to listen on the specified port
- The server inspects the request (most often only the path), and launches the server plugin needed to handle the request (corresponding to the server language you use, PHP, Java, .NET, Python?)
- The plugin gets access to the full request, and starts to prepare a HTTP response.
- To construct the response a database is accessed. A database search is made, based on parameters in the path (or data) of the request
- Data from the database, together with other information the plugin decides to add, is combined into a long string of text (HTML).
- The plugin combines that data with some meta data (in the form of HTTP headers), and sends the HTTP response back to the browser.
- The browser receives the response, and parses the HTML in the response
- A DOM tree is built out of the broken HTML
- New requests are made to the server for each new resource that is found in the HTML source (typically images, style sheets, and JavaScript files). Go back to step 3 and repeat for each resource.
- Stylesheets are parsed, and the rendering information in each gets attached to the matching node in the DOM tree
- Javascript is parsed and executed, and DOM nodes are moved and style information is updated accordingly
- The browser renders the page on the screen according to the DOM tree and the style information for each node
- You see the page on the screen
At any point in the above something can go wrong. Also each browser has their own version of a "render engine" which is used to parse all the CSS, Javascript, HTML, etc.. Because each browser is different things which work in one browser may not work in another, or even a different version of the same browser. However, browsers are updated all the time, along with the render engine it uses. Although Chrome is very popular, it's render engine Blink isn't the best IMHO, I think the Geko engine used by Firefox is probably more strict regarding standards and rendering implementation.
You can try downloading Firefox here: https://www.mozilla.org/en-GB/firefox/new/ and see if it solves your problems.
Since your the only person experiencing the issue we can safely assume the problem is local to your PC. So, there really isn't anything we can do for you from here.
EDIT: Oh, and firefox doesn't send your information to the Google Mothership.
2 x
: Read 150 books in 2024
My YouTube Channel
The Autodidactic Podcast
My Author's Newsletter
I post on this forum with mobile devices, so excuse short msgs and typos.
My YouTube Channel
The Autodidactic Podcast
My Author's Newsletter
I post on this forum with mobile devices, so excuse short msgs and typos.
-
- x 7661
Re: Onscreen Appearance of LLORG
Thank you very much for the detailled explanation, which was so well crafted that even I understood!rdearman wrote: The thing you are describing is most often caused by something called CSS, or cascading style sheets ... Since your the only person experiencing the issue we can safely assume the problem is local to your PC. So, there really isn't anything we can do for you from here.
They want you to believe this!rdearman wrote: ... Oh, and firefox doesn't send your information to the Google Mothership.
0 x
Return to “Technical Support and Feature Requests”
Who is online
Users browsing this forum: No registered users and 2 guests