I'm making my personal website using a lot of jquery and the basic HTML5/CSS3. I just put some $(document).ready(), maybe that's where the issue comes from..
As I'm trying to see how browsers deal with it, I figured out that google chrome keeps on loading (something but what?) the page. I mean the wheel is spinning in the tab panel and at the bottom of the page, I have a bar saying "Waiting for localhost...". I don't have this issue with Internet Explorer for instance.
How can I find where the problem comes from? Is it just a bad interpretation of chrome? The bar at the bottom is actually quite annoying...
I've been through this:
Try to load the page in anonymous mode (⇧+⌘+N) - if there is no spinning
I would bet on an network activity caused by an extension - check the list (chrome://extensions/) and try to disable a few
Related
I am opening a simple web on Chrome for Android. I need to hide the address bar without user interaction. I tried the window.scrollTo(0, 1) method, which isn't working. I think the newer browsers don't support it, but I installed Chrome 36 and it still didn't work there. I know that is a hack. But the whole web page I am displaying is a hack and I can't do anything about that. I can't use other browsers. I can't use fullscreen, because that requires user interaction. I can't make it into progressive app.
As soon as I manually scroll, the address bar disappears. So I thought maybe I could somehow simulate that. But I am lost with ideas.
I doubt you would be able to hide it since that would be a risk to the security of the Android user.
I have a php page that hangs for 3-10 seconds after the page loads, you can't even scroll up or down, or close the tab when this happens. (the chrome loading gif still loops tho) Happens in Chrome and IE.
Chrome Timeline: http://imgur.com/wF5Pioz,KRbnxIm#0
Shows ContentVeil.js repeating over and over. I think it is client side(?), I did a grepWIN to search for ContentVeil, with no luck, and it doesn't show up in Chrome Network tab.
Chrome Profile: Second image, from above link.
I think this shows the issue at the anonymous function from meta-boxes.min.js, ln 1.
meta-boxes.min.js: http://pastebin.com/yqtJyqB1
Unfortunately line one is a function that encapsulates the whole script. I don't know js very well, I tried to just remove each function one by one but that just created more errors.
Any ideas on how I could find the source of the problem would be much appreciated.
It's part of the Evernote web clipping extension, and it's hooks DOM events, causing massive slowdowns if you are doing large amount of dom changes.
I'm a Chrome user and would be lost without Firebug, but one issue has always annoyed me. Namely, the fact that the Firebug console doesn't appear below the site you're viewing (ie the way it behaves in Firefox). Instead, the console sits above the site, obscuring the footer and content. It's a little thing but annoying all the same.
I understand that this is because of the way Google restricts Chrome extensions but is there a way around this particular issue?
I haven't found a solution anywhere. So, with some help from other stack overflow threads, I came up with a very simple function and as I couldn't find much about this, I thought I'd post it here for anyone with the issue.
I'm not a JavaScript programmer, but I do use jQuery. As such, I run this inside jQuery's ready method. Once the site has loaded, it'll check to see if Fire bug is open, if so, it simply adds a 400px bottom margin to the body. Obviously, if your console is bigger/small than that, just change the size inside the jQuery code.
It won't however change anything if you open the site and then open Firebug. It's nothing major, just open Firebug then refresh the page an it'll work.
// add body margin if firebug is open
if (console.log.toString().indexOf('apply') != -1 && navigator.userAgent.toLowerCase().indexOf('chrome') > -1) {
$('body').css('margin-bottom', '400px');
}
Hopefully this will be of use to somebody.
EDIT:
WARNING: This can possibly cause your jQuery to stop working in Internet Explorer. So, just remove this if you find that your jQuery doesn't work.
Instead of modifying your webpage's CSS code which may have adverse effects, you should just detach Firebug Lite in Chrome, then position that popup window under the resized Chrome browser window.
To perform this, just press the center button in the Firebug Lite window located at the top right corner.
Right-click the image below and view in full size if that helps:
Open Image in New Tab / View Image
This way, you'll have two separate areas that don't overlap yet play nicely together.
Per Stan's comment above... about what does Firebug Lite provide extra when compared to native Chrome's Developer Tools, I would have to say it provides familiarity and a great DOM Tab that Chrome lacks.
More importantly thought, you can actually use BOTH consoles at the same time.
This allows easier monitoring of two different panes and with a multi-monitor setup this can be a useful scenario. Even with a large monitor things look good.
Right-click the image below and view in full size if that helps:
Open Image in New Tab / View Image
I have written a word game using HTML5 canvas tag and a little bit of audio. I developed the application on the chrome web browser on a linux system. Recently during the testing phase it was tried on safari 5.0.3 on Mac and the webpage froze. Not just the canvas element, but interactive element on the page froze. I have at some times experienced this problem on google chrome when I was developing but since the console did not throw any error before this happened, I did not give it much credence. Now as per requirements I am supposed to support both chrome and safari but this dismal performance on safari has left me shocked and I cannot see what error can be thrown which might lead to such a situation. Worse yet the CPU usage on using this application peaks to 70-80percent on my 2yr old macbook running ubuntu... I can only but pity the person who uses mac to operate this app, which undoubtedly is a heavier OS. Could someone help me out with a place I can start with to find out what exactly is causing this issue.
I have run profiles on this webapp on google chromes console and noticed that in the heap spanshot value increases steadily with the playing of the game, specifically (root) value which jumps up by 900 counts. Any help would be very appreciated!
Thanks
EDIT: I don't know if this helps, but I have noticed that even on refreshing the page after the app becomes unresponsive the page reloads and I am still not able to interact with the page elements but the tab scroll bar continues to work and I can see my application window completely. So to summaries the tab stops accepting any sort of user interaction inside the page.
Edit2: Nop. It doesn't work still... The app crashes on double click on the canvas element. The console is not throwing any errors either! =/ I have noticed this problem is isolated only to safari!
Edit3: Okay, so I performed some other tests today. I isolated the HTML5 widget and its HTML data only and ran it on safari locally to reproduce the error. Alas it works well! So I tried playing the game from my server without Facebook integration, and it works fine again! So The issue crops up only on safari on MAC OSX, while the widget is on Facebook canvas as a Facebook application. I am very hard-pressed to come up with a reduced test case scenario for this app... =/ It gets weirder, the game works well on safari for windows. Also after the tab freezes the other tabs continue to be responsive and well working. This tab too closes on clicking the close button and stuff, but if I load another page on this same tab after its frozen the page loads in the tab canvas, but I cannot interact with it. Not even google.com! So I am sure there is no bug with my game but its a safari bug... Will soon file a bug report, thanks for all the help people... :)
What you should do, in one sentence: Reproduce the problem with as little code as possible.
Start removing parts of your app until you find nothing that can be removed while still preserving the error. Start by throwing out external resources (css, images, etc) and leave just the html and javascript. Try removing the audio. Try removing as much gaming logic as possible. Try removing all user input code.
If this truly is a bug in Safari itself and not in your code, it should be possible to create a very small code example. Until you have that, saying "my web app doesn't work in safari", without any details or examples, will get you nowhere.
I'm using HTA with frames, the left frame controls the main frame and show pages in it (like a navigation panel), for example: You press the 'google' link on the left and it opens it on the main window. (This isn't the primary HTA's purpose, but I just simplify it to explain)
Now the problem is when I'm trying to open a web page with bug reports - The HTA is keep informing me about the page's bugs and sometimes the page even doesn't function properly. (The bug reports are not about pages that I created!)
The same pages works perfectly in IE.
It is important to mention as in the title, that I or any of the HTA's users doesn't have admin privileges in the system.
I googled it for a long time, but never found a solution, I will really appreciate any helpful tip or solution to the problem.
Thanks,
Rotem
you have a couple options to get around this problem. The best option is to just disable the setting "display a notification about every script error" in Internet Explorer. Since you are running an HTA you could modify the HKEY_CURRENT_USER registry setting programmatically (or just manually do it once.)
The second approach is definitely more of a hack but it's how I solved the problem myself when I created a tabbed browser in an HTA before IE had tabbed browsing. Instead of navigating to the URL in the iframe, you'll instead want to AJAX request the content, prepend a script block that sets window.onerror to a function of your chosing. Then inject the entire contents into the iframe. This approach will swallow any errors and give you the option of reporting them as you wish.
In addition to injecting the onerror script, you will also need to do some pre-parsing on anchors so that subsequent clicks are routed through the ajax injection handler. This proved to be pretty complex because you essentially begin writing your own browser. I still have the source code to the project so I'll publish it to a bitbucket repo and let you explore my approach.
Otherwise the last option is to send an email to the administrators of each site and tell them to fix their friggin bugs!!!! but I doubt that option will pan out for you :D
EDIT:
After loading up the old project I have discovered that the solution is less viable than it used to be. The x-frame-options header directive now prevents google.com from even loading in an iframe since IE8. And for some reason the window.onerror trap isn't catching the errors in the iframe (could be a nested iframe issue actually, but I don't have a viable solution for that.)
But I still had the option of checking the "Do not show this message again" option of the error dialog. That makes the error dialog stop reporting issues for me and it didn't require admin privileges.