Today I updated to Chrome 32 on Ubuntu 12.04, but tab title can't display Asian characters correctly, it displays typo instead. It works fine on Windows.
I've fired a bug for chromium project, however I still want to know if this is just for me or a common problem.
When I type "search" in Google, tab title shows:
When I type "検索", it shows:.
Can anyone reproduce this? In fact, I would love to fix this by myself but I may need some help on where I can find the code related to displaying tab title, the whole chromium code repository is just too big...
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've a really weird bug to hunt. It occurs on chromium (83) and chrome (84) but only on my Debian system. it does not occur neither on my colleagues Linux with chrome, nor on Firefox at my computer nor a any windows setup.
It that after submitting a matDialog in an angular-(9.0.6)-application, a routing (back) takes place which I can not explain. When I set persist logs on in chrome and chromium, I can see that after submitting the dialog, the browser somehow redirects. I searched all places in the code where router.navigate is called, but it's none if them. In Network-communication tab everything seems to be fine.
The bug is not reproducible on other machines. But on mine it happens with different program versions, with a local and online instances. I am quite desperate and have no clue what might be going on.
What I found is, that after the log-entry in the browser-console of the unwanted redirection there is a question mark:
The questionmark is blue, so it's not part of the URL, but part of the log-message. Does anybody knows what it could mean? Maybe the answer is a hint of what is going wrong here.
Btw. it's the same in chrome and chromium; both freshly installed respectively with all addons disabled.
In the end, it was far more trivial than I thought. There was a hidden submit in the dialog, to allow closing it by pressing enter. It had not to d anything with the browser or OS, but how we closed the dialog, by pressing enter or by using the "ok" button.
<input matInput [formControlName]="bla" (keyup.enter)="matform.submit()">
So this morning my Chrome Stable version updated from version 78 to 79.0.3945.79, and with this new update the code hovering is broken in the dev console.
To explain more exactly, if you put a breakpoint on some code line, and it triggered, in the previous versions you could have hovered a variable (this.something) and a small tooltip with all the variable data would have appeared above it. Since the 79 version this doesn't work anymore and no tooltip appears when hovering over such an element, or when highlighting one or one line of code like "object.name1.value", where before this .value was shown.
Did anyone else encounter this problem? I also had this on 79 when it was in Beta but I thought it was a bug so hence I used stable.
Looks like a bug. For now, you can install chrome canary - Version 81. Thx to https://support.google.com/chrome/thread/16855096?msgid=22548123
In the Chrome web browser, if you're somewhere in the middle of a webpage, and click there to indicate where you are, and you start searching for a string using ctrl-f, the search always starts from the beginning of the webpage. I used to mostly use Firefox, so this is surprising for me because, in Firefox, this works as expected - the search starts off from where you clicked. Is there any way to get the same behaviour from Chrome?
Thanks in advance.
nope, but it is requested: https://productforums.google.com/forum/?fromgroups#!topic/chrome/h9cZN8WOBhw
I suggest you second the request.
Edit: third it