We return to the Opera something for which we love her so much (or once again about the Internet accelerator;)
I have been a loyal browser user for 10 years. Despite the strong closeness of the Opera (well, extensions, but even to the clipboard it copies not like the others), its engine is a real drug that keeps me in the camp of fans all these years.
Recently, however, I notice a rather annoying thing: the pages are not shown on the fly, immediately after the start of the download, but are displayed with a delay . I found out the reason during one of the discussions on Habré, when my opponent ( egorinsk ) could not understand what my rendering of the pages opened from the cache in Google was, slows down (everything flew away from him). It turned out that javascript is constantly disabled!
After reviewing the pages with javascript enabled and disabled, I found out that Opera simply gives a crazy priority to rendering with javascript. You can understand the logic: now some sites are generally web programs that are not of any interest without js. However, Opera's developers have always been famous for preferring rendering speed, page rendering on the fly, and user comfort. After all, with CSS, things are exactly like this: while loading the same blogs with CSS themes, we first see the ugly plain html, which is then put on in CSS clothes.
')
Perhaps a habrayuzer with 10 megabits will not notice anything, so I want to ask - what about comrades with not very fast connections? Also? Or maybe someone found a solution to this problem?
Megascabo cam. Kalan !
We cut in the opera: config # Extensions | DelayedscriptExecution parameter - and enjoy the shots that we love Opera so much!
PS For some, the parameter is not saved in any way when the Opera is restarted. It can be found and corrected in operaprefs.ini
Recently, however, I notice a rather annoying thing: the pages are not shown on the fly, immediately after the start of the download, but are displayed with a delay . I found out the reason during one of the discussions on Habré, when my opponent ( egorinsk ) could not understand what my rendering of the pages opened from the cache in Google was, slows down (everything flew away from him). It turned out that javascript is constantly disabled!
After reviewing the pages with javascript enabled and disabled, I found out that Opera simply gives a crazy priority to rendering with javascript. You can understand the logic: now some sites are generally web programs that are not of any interest without js. However, Opera's developers have always been famous for preferring rendering speed, page rendering on the fly, and user comfort. After all, with CSS, things are exactly like this: while loading the same blogs with CSS themes, we first see the ugly plain html, which is then put on in CSS clothes.
')
Perhaps a habrayuzer with 10 megabits will not notice anything, so I want to ask - what about comrades with not very fast connections? Also? Or maybe someone found a solution to this problem?
The decision was not slow to appear!
Megascabo cam. Kalan !
We cut in the opera: config # Extensions | DelayedscriptExecution parameter - and enjoy the shots that we love Opera so much!
PS For some, the parameter is not saved in any way when the Opera is restarted. It can be found and corrected in operaprefs.ini
Source: https://habr.com/ru/post/66628/
All Articles