New issue
Advanced search Search tips

Issue 650988 link

Starred by 3 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Sep 2016
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Styles not being applied to application page due to JavaScript events not being consistently executed

Reported by fergalga...@gmail.com, Sep 28 2016

Issue description

Chrome Version       : Version 53.0.2785.116 m (64-bit)
URLs (if applicable) : N/A
Other browsers tested:
    Firefox: OK
         IE: OK

What steps will reproduce the problem?
(1) Application Page whose style is applied on the execution of a JavaScript 
Publish/Subscribe event
(2) On the first occasion the page is rendered, the event is processed correctly and the styles are applied.
(3) However, on subsequent page loads, the styling is not applied as the event
is either not being fired/event is being fired and the synchronization of the 
event processing is not correct.
(4) This leads to the styling not being applied to multiple application
pages on an intermittent basis.

What is the expected result?
Styling is applied to the application pages on a consistent basis based on
the events being fired and processed correctly.

What happens instead?
Styling is applied to the application pages on a consistent basis based on
the events being fired and processed correctly.


Please provide any additional information below. Attach a screenshot if
possible.
The styling is being applied correctly on all Chrome versions prior to Chrome 53. We have also taken the current beta channel (54) and it also does not work on that version. However, the issue seems to have been resolved in Chrome 55 (current dev channel).

Have any changes been made to the way Java Script events are being handled in Chrome 53 which did not exist in Chrome 52 and have been reverted in Chrome 55?

 
แคลนออฟแคลน

Hi folks,

The issue seems to have been resolved in later versions of Chrome.

 - The issue first occurred in Chrome 53.0.2785.116 (released September 14th). The issue is no longer reproducible in Chrome 53.0.2785.143, which was released yesterday.

 - Chrome 54 beta channel has updated to "54.0.2840.41 beta-m (64-bit)" and the issue is fixed there (Was broken in "54.0.2840.34 beta-m (64-bit)").

It seems some issue which was introduced has been addressed in those later versions of Chrome.
Status: WontFix (was: Unconfirmed)
Closing as per #2

Sign in to add a comment