Remember, users only know a fraction of what you do about your app / site / product / service. Worse, new users know literally nothing about it. They don't know or care about your golden paths. They only know what they've experienced and whether they've gotten it work for them.
-
-
Replying to @DotProto
Indeed! Users often tell me there is a bug in my extension whereas it's just yet another regression in Chrome (yes, yet another one today). It's hard to explain I'm not responsible for this. I'm slowly beginning to recommend them to switch to Firefox to fix this issue.
1 reply 0 retweets 0 likes -
-
Replying to @DotProto
Basically, when SingleFile tries to retrieve a frame content, it sends a message to the corresponding content script. It also creates a fallback timeout because there the content script might not be present. In the past a delay of 750ms for this timeout worked fine in Chrome.
1 reply 0 retweets 0 likes -
Now, I have to set it to 5000ms otherwise the content script in the frame does not have the time to return the content to SingleFile. IMHO, I consider that a max. delay of 5000ms of waiting time when receiving a message from the content script is HUGE.
1 reply 0 retweets 0 likes
I profiled the code. I confirm there are some parts of it (e.g. DOM operations to read computed styles) that run much faster in Firefox than Chrome. This is the cause of the issue. I'll try simply to get rid of the timeout to fix it.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
could you share a link to the relevant bug?