I have an HTML table with at most 25 columns (usually 5 or 6) and at most 25 rows. Each cell in the table contains a custom Web Component. These are minimal web components. For example, one wraps a number and you can set number formatting (e.g. format as currency) via the attributes. Another just displays a formatted string, etc. I am adding these components dynamically using appendChild on the td.
These Web Components are all using the Shadow DOM - as recommended in the documentation. So I create this simple table (6 rows and 25 columns) and I populate cells with these Web Components. If I do this in Chrome, my system crashes requiring a reboot (sometimes by forcing a shutdown). I tried this in Firefox, and the table renders in less than a second. Also I tried this in Edge and it crashes there too.
I tried re-doing my Web Components to remove the Shadow DOMs and voila, it works fine in Chrome and Firefox.
I don't want to do these component without the Shadow DOMs. Does anyone have any ideas?
Thanks
Update: this is still a problem. I tested in Edge browser and it does indeed work there (albeit a bit slow). Also tested in Safari/ MacOS and it works there too.
What a shame… I have to tell my users they can’t use Chrome and prevent the page from loading.
Update 9/2/2022: Without any changes to my code it is no longer an issue. The only explanation I have is that it might have been happily addressed by a scheduled Chrome update.
Now however, even though my table loads OK, if I open Developer Tools immediately after the table loads, I get a crash with error: 'Debugging Connection closed. Reason: Render process gone.'
Update 9/4/2022: I was overly optimistic about this error. I started testing my app again in Chrome today and the original problem still exists. I create my table in Chrome, interact with it in various ways (e.g. dynamically add a column, add an icon prefix to cell contents of a column, dynamically add a column with a drop-down menu in each cell, etc.) and eventually Chrome will crash.
I no longer expect this to be fixed. I logged a bug report with chromium.org and that is all I can do.
Related
I have a small database project where users can attach files to records. Mostly pdf and word docs. I am using the attachment type fields that access provides because I want to get more familiar with them. I have a continuous form that shows the attachment field using the Picture/Symbol view option. Most of the time, but strangely not always, the attachment symbol shows this black background behind its symbol. The black background does not cover the whole field but rather only the picture for the attachment type (Word, PDF etc.). The field itself is set to transparent, which is neccesary for my row highlighting to work. Does anyone know why this is happening? Is it a bug? Some way to fix it? It had worked when I had first set it up but upon restarting my computer and reopening the project they turned black and are now stuck that way. I removed them later for some reason and re-did the whole thing, upon which it seemingly worked but after restarting it went black again. There is no difference between using the view settings Picture/Symbol and Symbol.
Visual Aid:
Update 1:
The black backgrounds are seemingly random. I set the view option to Paperclip, restarted access, then set them to Picture/Symbol again and now I get this:
Closing and opening the file appears to turn the backgrounds black. Changing the view type back and forth inbetween can fix some, but not always.... I'm really not sure what's going on.
Update 2:
The issue is seemingly not affected by transparancy settings. Changing the Background color of the field has no impact either. The issue also persists when making a new form from scratch and adding the Attachment type field to it. It also carries over from one pc to another, so unless both have the same issue in their windows installation I don't think that is the root cause either. Compress & Repair did not help. I am only using one attached file per record.
Update 3:
I have had no luck consistently reproducing the issue. Most of the time, about 80% of it I am estimating, the issue persists. Some days, when launching access, the issue is resolved partially for either the word icon, or the pdf icon. On some days the issue is resolved for all icons as in the picture below. Almost always, after closing and opening access, the issue will immediately reappear for all icons. Closing and opening the form only and keeping the file open is fine, the issue stays resolved. Really not sure how to go about this.
My Access version:
Version 2205 Build 16.0.15225.20028
My Windows install:
Microsoft Windows 10 Pro
10.0.19044 Build 19044
So, updated to windows 11 and the issue is solved. No idea what was wrong exactly but it turns out it was related to the windows install. So, some kind of a bug in Win 10 is my guess, since it was happening on two different machines both running win 10.
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.
I am using OpenRefine to clean text from a CSV file. I've been working on the same project for several weeks, and it was working fine until this week.
I am trying to use the 'Cluster and Edit' function from the 'Edit cells' menu. When I use the 'fingerprint' and 'ngram fingerprint' keying function, the frame that opens up inside the browser window is sized appropriately, and I have access to all the buttons and selection menus. However, when I try to use the 'metaphone3' keying function, the frame that opens up is way wider than the browser window, the sliding selection boxes that usually appear in the right side of the frame are not visible, and the buttons across the bottom of the frame ('Select All', 'Unselect All', etc.) are not available. I'd really like to be able to use this keying function option again. Does anyone know what's going on, or how I might be able to fix it.
I am using the OpenRefine 3.3 beta, although a similar issue was happening earlier this week with all keying function options in 3.2 (all were working fine in 3.2 as recently as Friday, 10/25/2019). I am using Firefox, although the same issue happens in Internet Explorer. The system OS is Windows 10 Enterprise.
Thanks in advance!
I've been working on a new website and practicing my JS/jQuery/AJaxy skills. Last night I wanted to take a look at how long the page was taking to render and see if there were any areas I could clean up to increase speed. While the page loads in about 200 - 300 ms every time, I'm seeing a large amount of blank space between resource loads under the network inspector.
http://i.imgur.com/7ng6m.jpg
Has anyone else seen this or know what I can do to minimize that time (talking about the blank space between like the html and the first css file)?
Quite possibly it is caused by the extensions you have installed. AdBlock, LastPass and Google quick scroll took altogether about 200 ms on my machine.
Unfortunately, these extensions are invoked on every site and block loading the additional resources.
Try it with out of the box browser setup, the loading time will increase tremendously.
You've got a bunch of images loaded just after the page has been loaded (the load and DOMContentLoaded events have fired - the blue and red vertical lines across the Timeline). I can see that the images are loaded by the JQuery library (the Initiator column), perhaps to build a gallery or something.
So, the case is that JQuery loads the images after the page load, presumably in the onload handler (this can look like $(document).ready(handler) in your code, but other options are possible, too).
The delay between the initial page load and requesting the first resources is almost certainly caused by Chrome extensions. To find the culprit: Record a timeline in the Timeline tab in Chrome Developer Tools; Identify the scripts that are running during the Parse HTML phase; Work out which extensions they're from.
To record a timeline:
Open the timeline tab and click record.
Reload the page and then stop the recording. (A couple of seconds should be enough.)
To find the culprit:
Find the first main Parse HTML block on the timeline. On the row below you will probably see one or more Evaluate Script blocks. These are the culprits.
Click on one of the Evaluate Script blocks and find the script name in the bottom pane. Mouse-over the script name. The tooltip will have the URL of the script, which should be of the form chrome-extension://{long_identifier}/{path}
Memorise the first few letters of the identifier and search for it in the chrome://extensions/ page. This tells you which extension is causing the problem. Try disabling it - you should see a difference.
Repeat for the other Evaluate Script blocks.
In my case, I have 20 extensions installed but only two were causing a delay: LastPass and Fauxbar. I've chosen to leave them enabled because for me the productivity benefit of these extensions outweighs the downside of the added latency.
I have a drag and drop upload script which works fine on chrome and firefox. However, on Safari, it has an issue with retrieving the file size. It returns 0 bytes for the file size, but strangely, it will occasionally return the correct file size. This is around 1 out of every 10 times.
I am getting the files list via a drop event like so:
var files = event.dataTransfer.files;
alert(files[0].size);
And upon trying to use the size method, I get 0 bytes in return. Does anyone know why this is happening?
The file api is slightly different to the standard. Safari 6 will change that.
Source: http://www.thebuzzmedia.com/html5-drag-and-drop-and-file-api-tutorial/
Safari's implementation has some strange bugs, however. Occasionally, I've noticed in my own use of this feature that your first drop might stall and not go through. Adding a simple asynchronous request to a blank page prior to completing the upload seems to defeat that bug.
Guide for Safari 5: http://www.deadmarshes.com/Blog/20110413023355.html