I found a couple of rather glaring bugs in SWFAddress, involving IE-based browsers. Both of the following occurred in SlimBrowser (15,000,000 downloads on Cnet) and one in Avant (also several million downloads on Cnet).
Both bugs occur when returning to the original startup screen of a flex app via the back button. Both of them are repeatable using the already compiled sample Flex app that comes with the most recent SWFAddress 2.4 full download (but I have also repeated them after recompiling, and with other flex apps as well.)
Bug 1:
Open SlimBrowser and then open the SWFAddress Flex sample app in a single tab (make sure all other tabs are closed). In the flex sample app click one of the menu bar selections just to take it to another screen. Now hit the browser back button to return to the original screen. Then right-click the browser window tab for the Flex app and select 'close', to attempt to close the Flex app browser window. It causes the browser to crash.
Bug 2:
Modify the code for the starting page of the Flex sample app mentioned above to include a hyperlink to some other website. Now repeat the steps from Bug 1 to go to a different page of the sample app, and then return to the starting page via the back button. (Makes no difference this time if other browser tabs are opened.) Now click the hyperlink you created to navigate to some other site. On the other site the back button is disabled and you can't return to the Flex sample app.
I can of course attempt to debug this myself. Just didn't know if anyone wanted to save me the trouble. Also is anyone still maintaining SWFAddress, and do they even care about this sort of thing. I know people tend to loathe IE so don't know if they just decided not to support it. Also it would include scores of 3rd party browsers that have nothing to do with Microsoft, other than using the IE engine behind the scenes.
why don't you add a new issue on the swfadress bugtracker?
Related
We have a phonegap/ionic application targeting iOS. We have been testing with the ipad air simulator (xcode) and ipad air (10.3.3), ipad Pro (11.0.3).
The app is an ionic (v1) app that downloads and loads stand alone html files (the files contain css, html, js in one doc). The documents are typically long forms. In all test environments we are getting odd behavior with selects/drop downs.
When you click/tap on a select the options will appear correctly.
Then when you click/tap somewhere else, blank space or another input field you will usually get the select options bubble again but it will be empty.
In the above image I made my selection from the options and then clicked into the next field.
This was intermittent at first and now it seems to happen all the time. It seems like it has something to do with losing focus but I am unable to see why this is popping back up. I haven't found anything very useful from searching online in regards to this problem.
UPDATE 11/7/17
After more thorough searching this seems to be due to building the app with xcode 9 and/or the use of UIWebView vs WKWebview. I also looked through the code more to see we were already using WKWebView not UIWebView and the problem is still present. As someone mentioned in this thread.
Good thing is Cordova has support for WKWebView too. You have to install the plugin: cordova-plugin-wkwebview-engine
My Angular 2 Application is slow to respond (1-5 seconds) to key input, button clicks, tabbing across inputs, etc. only when Chrome Developer Tools is open. Material 2 animations also become slow and choppy.
I've been developing this application for three months, and use Chrome DevTools every day. This issue cropped up seemingly overnight.
What I know:
I stashed all pending application changes to revert my application to a time when this was not a problem. The issue persisted.
Chrome DevTools doesn't seem to slow down any other application (ie. google inbox, google maps) in the same browser session.
Maddeningly, when I run the DevTools' Timeline "Record" to try to gain visibility into the issue, the issue disappears and the page reacts at normal speed again! I assume this is the best clue that I have, but I don't know the internal workings of DevTools well enough to know how "Timeline Record" changes things.
I've restarted Chrome and deleted all cached data.
Nothing of the sort happens in Firefox or IE when I open the Developer tools in those.
Any recommendations on where to look next would be greatly appreciated!
Final answer:
Remove all breakpoints
Even if they're not getting hit this fixed it for me and got performance back to normal.
May be a bigger issue if you have logging breakpoints - so try deleting those first if you're attached to your breakpoints.
Previous answers:
I came up with a workaround - although still not really figured out what is actually wrong.
I also discovered a bunch of tools I didn't even know existed that I'd skipped over before - they're under More tools.
Start by opening the Performance Monitor. This shows a nice CPU graph isolated for your Chrome tab - the Windows task manager is as useless as it ever was.
This is the behavior I got when choosing a date from mat-calendar. No other logic running - just selecting a date. I removed everything from app-component and just put a mat-calendar and it took ten seconds to change the date!
Other controls are generally fine. I could open dialogs, use combo boxes etc. and nice and fast. But selecting a date gave me this nonsense:
I tried emptying local storage, clearing cache, etc. and then I changed port number for my website. I simply changed dev.example.com:44300 to dev.example.com:44301 - in other words Chrome now thought it was a different website.
This is what it looked like after I switched port number.
I also got the same effect using a reverse proxy server - which put my local machine on the internet - so I could try to duplicate the issue from other machines. I could not.
So hope that helps someone - still no clue what's in the cache for this server that is having such a massive impact on performance. But for sure it's not just my code.
Here's a few other things to try:
Test with --aot flag
This didn't make a difference to me, but good to narrow things down.
Add some controls that don't do anything (as a control)
This way you can find if some specific action or control is causing the slow down. You should of course be able to toggle these instantly.
Just toggle them on and off, hide something.
<mat-radio-group>
<mat-radio-button [value]="false">
bloop
</mat-radio-button>
<mat-radio-button [value]="false">
bloop bloop
</mat-radio-button>
</mat-radio-group>
Enable Rendering debugging options
Make sure you aren't re-rendering the whole page constantly
The rendering option above will show this to some extent, but one thing I like to do is just add a random text box - type in it and if the text subsequently disappears you know that control has been rerendered.
<!-- yes, just a standard text box -->
<input type="text"/>
Just hide things with *ngIf="false"
Hide controls (yours and third party) and see if anything is causing problems.
For me I'm currently suspecting mat-calendar is causing issues - but I'm still thoroughly confused as to why enabling 'Record' makes the problem non existent.
I've fixed the issue, but I'll never know what was causing it. Likely a setting that I had accidentally changed.
I deleted the Chrome App and reinstalled, everything is back to normal. I'm going to leave this question open in case anyone else has this problem or wants to contribute.
It is normal for every web app to run slowly with Chrome dev tools opened.
Especially if you have inspect tab open, that it's like a new page opened in the same time + has animations on any block render.
We had this issue today at a colleagues workstation. Turned out that it was a chrome-extension (don't remember, something with "ghost" in its name). So maybe try out using guest-mode and check whether the issue still occurs. If it doesn't, successively reactivate the extensions to see which one is causing the problems. If it still occurs, follow the other proposed approaches.
"I'm looking for different Chrome apps to make my pages darker/inverted to reduce eye strain, I found some apps that work but the only thing left, which these apps doesn't seem to override, is the White Blank page.
When a new page is loaded, Chrome first displays a White Blank page, while the page is loading then displays the website's content. Is there a way to override this While page to say Black? At the moment, everytime I click on a link or open a new webpage, the screen goes from darkcoloured (through inverted/darkening page apps) to the White Blank screen for a brief second then the new page loads in a dark colour again. This acts like a "White Flash" by the screen everytime a new page is loaded and causes further eye strain. This is why I want to know if there is a way to override this White colour to Black."
This question was already asked before in here, but the answers suggested back then do not seem to be working on my current version of chrome 49.0.2623.87 m.
The links that I have referred to already :
-This
-comment 261 here
-This
I created two files manifest.json and script.js in AppData\Local\Google\Chrome\User Data\Default\Extensions\
and did the "load unpacked extension" and that did not work either.
Edit 2021-01-01
Install chromium-based Brave web browser as a drop-in alternative to Chrome. Then:
Install DarkReader
Click Settings > Appearance > Brave colors > Dark
Open new tab and click Customize in new tab page to get an acceptably dark appearance:
Additional Benefits to Brave:
Brave is forked off of chromium, so generally behaves the same as chrome. It prioritizes user privacy and comes built-in with Ad Blocking capability that is also very easy to disable as you're browsing. Plus many other features I'm not mentioning here.
Original Solution (If you really don't want to use Brave)
As of April 2016, this issue has been pending for over 8 years (aside from the intermittent work-arounds that no longer apply as you pointed out). If you haven't already, please consider "starring" these reported issues.
Current Reported Bugs:
https://bugs.chromium.org/p/chromium/issues/detail?id=1373
https://bugs.chromium.org/p/chromium/issues/detail?id=470669
https://bugs.chromium.org/p/chromium/issues/detail?id=311
https://bugs.chromium.org/p/chromium/issues/detail?id=457714
https://bugs.chromium.org/p/chromium/issues/detail?id=128290
https://bugs.chromium.org/p/chromium/issues/detail?id=119871
https://bugs.chromium.org/p/chromium/issues/detail?id=409378
https://bugs.chromium.org/p/chromium/issues/detail?id=126341
https://bugs.chromium.org/p/chromium/issues/detail?id=64317
https://bugs.chromium.org/p/chromium/issues/detail?id=530026
Especially the first two links appear to be gaining some traction. More users that support them being fixed helps gain more attention and allows you to monitor progress from email notifications (or you can unsubscribe).
Report This Issue:
Next, submit feedback to chrome through your browser following these steps:
Open Chrome and click the "hamburger" menu on the top right corner
Click Help > Report an issue.
Add detail similar to the following:
Between page loads and new tabs being opened, there is a brief moment
where the entire browser screen is painted white, causing severe eye
strain.
This issue has been referred to in the following chromium issues:
https://bugs.chromium.org/p/chromium/issues/detail?id=1373
https://bugs.chromium.org/p/chromium/issues/detail?id=470669
https://bugs.chromium.org/p/chromium/issues/detail?id=311
https://bugs.chromium.org/p/chromium/issues/detail?id=457714
https://bugs.chromium.org/p/chromium/issues/detail?id=128290
https://bugs.chromium.org/p/chromium/issues/detail?id=119871
https://bugs.chromium.org/p/chromium/issues/detail?id=409378
https://bugs.chromium.org/p/chromium/issues/detail?id=126341
https://bugs.chromium.org/p/chromium/issues/detail?id=64317
https://bugs.chromium.org/p/chromium/issues/detail?id=530026
Click send feedback
I would then recommend installing Chrome Canary, as some of the experimental fixes to those issues above will first appear in Canary.
Invert Computer Colors:
Finally, as a last resort, turn on color inversion and use the whitest chrome theme possible.
http://smallbusiness.chron.com/invert-colors-computer-43975.html
https://discussions.apple.com/thread/5780779?start=0
White theme (that is very dark when inverted):
https://chrome.google.com/webstore/detail/minimal-white/clcbojcafbggjenbeflknhfimpcikmlc?hl=en-GB
Significantly better in Chrome-Beta and even better in Chrome-Dev (chrome-unstable), almost unnoticeable.
Using Ubuntu-Cinnamon-Remix 21.04.
So if you visit http://movableink.com/ on Safari on iOS9.
Then click in the header on http://movableink.com/partners
On first visit or slower connections the entire page renders blank in safari.
This is a pretty standard page. There's no specific code to call out that might be causing this. This is a new page with a different css file, it's the first responsive page.
However, the text and content is selectable (but not here) and also if I check it out in the Safari developer inspector when the phone is plugged into a mac there is also nothing notable covering the page.
You may want to look in private browsing, you will want to open up the homepage first and then click on 'Partners'.
What could possibly be causeing this issue of the page disappearing?
I could reproduce this on my iOS 9 device very well if there was an ad blocker active (in my case: Crystal and Lionz). Without this ad blocker active the page was loading smoothly without a blank screen.
By using another ad blocker (e. g. 1Blocker) the page is also running smoothly.
For me the problem is only related to certain ad blocker apps on iOS.
I did some tests, it could be just request timing issues due to either un-optimised server code (like regenerating the whole site stack every first request from a client), or generating CSS.
On first load it is consistently 700ms, regardless of mobile or desktop. Safari will be more sensitive on the mobile as it processes not as many parallel resources after it has a list of url's to get.
If you are using a CMS, check for Optimising / Caching solutions in built into the system and switch that on, see if it changes the load times.
Another alternative is Cloud distributed CDN's such as Cloud Flare (free for basic, other plans for more intensive).
I've a test website on http://insstock.info/xxx/
With two sliders inserted into it:
Nivo Slider
DIV Content Jquery slider (Exact below of Nivo Slider)
second slider is expected to flip the content one by one; the code and scripts are set accordingly!
It is showing no error in Chrome developer tool Console panel!
Can anyone Please help me to making this second slider work?
A couple of suggestions that I run through when I experience this behavior.
1) Clear the Chrome Cache
Chrome caches aggressively and frequently will return stale resources. You can clear the cache either by using Ctrl+Shift+Del, or prevent its use on the page by opening up Chrome Developer tools, clicking the gear icon in the bottom right, and checking "Disable Cache". Then reload the page with Ctrl+Shift+R. This will ensure you have the latest version of your resources.
2) Check the Network tab for any resources which are failing to load
3) Step through your code in the debugger to try to identify where things go wrong.
4) Start removing pieces more and more pieces of your code until you have a very small set that is exhibiting the issue. This is a great strategy for debugging generally, since it is much easier to debug something small than something big.