I'm working on an internal project and I'm running into a very strange issue. This project will be stored locally and ran from a shared drive. No web server or anything like that.
When I double-click the file to open it, everything renders correctly. If I hit refresh, it re-renders great, as well. However, when I open a new tab and paste the file-path into the address bar it -sometimes- renders incorrectly. It doesn't happen all the time, but I'm gonna guestimate that it does it wrong about 80% of the time, when pasting the file path into a new tab. Upon refreshing the tab, all is well again.
So my question is: what could possibly be causing this? Why doesn't it happen -all- the time? Since this is for internal uses only, I can simply let users know to hit refresh, so it's not that big of a deal. I'm just extremely curious why this is happening.
See below for screenshots. Left is the correct rendering.
Edit: A bit about the code: due to policies, I cannot simply paste everything here, but the elements are contained within a ul li that has text-align: left. Each element has float:right. Text labels are flushed left in the containing li
JSFiddle - static
JSFiddle - with JS
Related
I can't find anybody facing the same problem as mine.
Every time I click an image on google image, suddenly the whole page disappear, but I'm still able to click things just like everything is still there.
I already turn off all extension, use incognito mode, after finally I try to use inspect element, and found attribute stating "Opacity: 0" on the body. And after unchecking the box (Quick disable attribute in inspect element chrome) everything shows up again.
I'm so confused on why this is happening.
Does anyone have ever facing the same problem?
Or how do I fix it?
It's so frustrating, because I have to refresh the page, every time I click on an image, or switch between images
so I was having this one. in the end, it was a virus.
In my case, it was showing an AD screen on the main google page, and in the sources>gstatic.com it had a different source which also was in a [unknown] source.
dug a bit up and discover some adware was using gstatic as a proxy to show ads on all browsers.
I solved it by running malwarebytes, it found it pretty quickly and solved it for me.
Posting this here because I'm hoping it helps people who search for this issue in the future.
part of the log
i'm struggling with the classic HTML input of type file. I was using it on my angular application and i had freeze sometimes, the whole browser became unresponsive, and the only thing that works is the scroll.
You can't click any buttons, select any text or even change tab on the browser for about 5 seconds. I tried a lot of different file type and sizes and it doesn't change any of this, it even freeze sometimes when i don't select any file in the explorer and i click the close button directly.
So I thought it was my implementation that was bad and i went to the Mozilla developper website where you have an example and I have exactly the same behaviour. I also tried to take only the HTML from the Mozilla website and put it alone on a .html file and again, same behaviour.
This does not occur 100% of the time, but I would argue that on my end it does it about 60/70 % of the times.
I tried it on chrome and Firefox (both up to date), on multiple computer (all running Windows though) and i have the same behaviour on all of them.
I don't have any error or anyting in the consoles.
I don't know what to do with this, i'm pretty sure it can't be the file's input on the whole web that are bugged, but i tried a lot of various things with always the same results. Should i report it somewhere? ( if so, where? ) Or what would you suggest to do to investigate this further?
I couldn't find anyone discussing this issue on the internet apart for this thread that had no solution, they also say in this thread that the bug is not reproducible in Edge, but i just tried and it does the same thing.
Thanks for reading me and for any help about this.
Chrome freezes for few seconds when after any use of file field.
It was because I had a shortcut in "Quick Access" menu in windows explorer. This shortcut has been linked with a folder shared by network. I've removed this shortcut and everything is good now.
Same here, I have a mapped network drive that is not responding, this make a 5 seconds delay. After unmapping the drive, no more delay. The delay is the same in firefox or chrome.
Same here, if you want to remove it, on Windows 10, click on the icon Quick access (blue star), then right click on the dead link appearing in the "Frequent folders" panel on the right panel and choose "Unpin/Remove from Quick access". There should be no error message.
When I'm in Access and using a Tab Control, if I copy a button on one tab and paste it to the same tab, this button becomes visible on all tabs. In fact, I think all controls do (I know it happened with buttons and labels).
Is there a way to fix this, or do I have to delete the copied controls and re-draw them on the tab they're supposed to be visible on? Is there a setting that fixes this? I've got a few pages where it'd be handy to be able to copy a chunk of controls and paste them onto a different tab.
This is an old issue that needs to be closed out. The OP #Johnny Bones talks about his answer in the comments but never posted what he did to fix it as an answer.
The answer is that the object was pasted in at the wrong level, the form level. Form level objects are seen on every Tab Page.
To fix this
Cut the object again
Select the Tab Page you want the object to live inside
Paste it there
Move it to the correct location
I wanted to add an Google CSE to the gitbook instead of the normal search engine.
It's no problem to add the GCSE to the gitbook, only the result is weird.
If I go directly to a page I can see the Search Box and can use it normally. If I look at the code there is a div: <div id="__gcse_0">.
If I now go through another chapter the Search Box disappears and there is another div instead of the previous in the code: <gcse:search>.
After I refresh the page the box appears again. This happens on Firefox and Chrome.
Do somebody know what the problem might be?
I've been trying to figure out this same issue... So far, I can only get it to stay by placing the google script into an overriding layout.html - but this is not recommended, and it isn't ideal for most placements. I've also noticed that the CSS that is loaded through the script then gets lost when switching pages (like the script itself was previously) so this solution would also be a pain to re-add all the css files. So it's a super messy solution, and hopefully some one has a better solution out there.
When a site gets stuck in chrome with the 'loading www.site.com' status, Is there anyway to know which of the elements on the DOM is delaying the load? for example, it can be an external js file or image that is taking long time to load. I tried using the network tab in the DeveloperTools, but it only shows the elements already loaded and the time they took. I couldn't find a way to see which element is stuck.
I found a way that I'm not sure it works in all cases, but it did for me. I used the Timeline tab (now shown in the Performance tab), it's one of the tabs in Chrome Dev Tools.
Open Chrome Developer tools (F12 or CMD + Alt + I in Mac) and click the Performance tab
Make sure you drag the grey timeline bar all the way to the right, you want to see the most recent section of events so you can find what's getting stuck:
Check just down below the records sidebar. If you don't see this like in the capture below, try toggling the icons, there are different view modes. Now, going all the way down I found these. It doesn't look like that's going well. Obviously some kind of infinite loop in some random code:
I couldn't find out if it was an extension itself or some other bit of code. Clicking through I only could find // Copyright 2014 The Chromium Authors. All rights reserved..
Checking in Incognito mode clear of extensions, the website loads just fine.
I'd also advise to check the Console tab to see if there are were any errors that might cause the infinite loading thing. You'll often find clues there.