Odd Issue with Likes and Quick Replies

[Joey D]

@Jordan this is a weird one. When I click the "like" button on someone's post I now get a second window asking me to confirm it.

I'm also not seeing the WYSIWYG when I go to make a quick reply to a thread.

I tried clearing cookies and temp files just to be sure too. I'm using Google Chrome Version 71.0.3578.98 (Official Build) (64-bit) too.

 

[TJ13]

It must be a Chrome thing.
I am on FF 65. 64-bit.
I don't have any issues.

 

[Jordan]

It looks like JavaScript is turned off or you have some type of content-blocking plugin installed, like NoScript, Ghostery, etc.

Adjust your browser or plugin settings and that should resolve it for you.

 

[Joey D]

Ah, looked like it was a Java issue. Thanks!

 

[FoRiZon]

It's also appears when you use Opera Mini with extreme compression because I'm a cheapskate at data plans.

 

[Jordan]

It's also appears when you use Opera Mini with extreme compression because I'm a cheapskate at data plans.

Ironically, that is actually causing you to use more data, not less.

 

[Aphelion]

Ironically, that is actually causing you to use more data, not less.

Does it? How do you know...?

 

[Jordan]

Does it? How do you know...?

Because it requires him to load a lot of additional web pages which cannot be cached by the browser.

Sending a "like" to the server via JavaScript (which Opera Mini's "extreme compression" is obviously blocking) sends around 300 bytes (0.3KB) of data. Without JavaScript, clicking the like button loads a ~6KB confirmation page and then reloads the thread page. If he liked a post in this thread, that will be another 13KB to download.

So, that's 19KB of total data required to send a "like" with JavaScript disabled, and 300 bytes (0.3KB) of data with it enabled. It takes longer and uses more battery, too. The difference would be even greater with larger/longer threads, and this is just one of the site features that it affects.

Sure, "extreme compression" mode blocked the download of the JavaScript files which are required to make all that work, which total probably 100KB in size. However, they only need to be downloaded one time and will be cached in the browser's memory for 30 days after that. It only takes a few likes, replies, or alert checks for the savings to immediately take effect.

 

[Aphelion]

Because it requires him to load a lot of additional web pages which cannot be cached by the browser.

Sending a "like" to the server via JavaScript (which Opera Mini's "extreme compression" is obviously blocking) sends around 300 bytes (0.3KB) of data. Without JavaScript, clicking the like button loads a ~6KB confirmation page and then reloads the thread page. If he liked a post in this thread, that will be another 13KB to download.

So, that's 19KB of total data required to send a "like" with JavaScript disabled, and 300 bytes (0.3KB) of data with it enabled. It takes longer and uses more battery, too. The difference would be even greater with larger/longer threads, and this is just one of the site features that it affects.

Sure, "extreme compression" mode blocked the download of the JavaScript files which are required to make all that work, which total probably 100KB in size. However, they only need to be downloaded one time and will be cached in the browser's memory for 30 days after that. It only takes a few likes, replies, or alert checks for the savings to immediately take effect.

Jesus . I had no idea it could cause that... makes sense though.

 

[FoRiZon]

Ironically, that is actually causing you to use more data, not less.

Thats odd. I think it depends on the website. The extreme compression one on Opera Mini does removes quite lot of unnecessary web layers for other websites.

I guess it's not for the minuscule kb type of saving data and more of the more macro-level.