I have some bugs with Chrome. Since a few weeks ago the placeholders don't behave, when I click on the input the placeholder should be hidden, but it stays there until I type. And also the location.href in js scripts don't work. When I click a link I should be redirected but nothing happens since I noticed the placeholder bug.
What could be the problem ? I tried reinstalling Chrome but that didn't fixed it.
According to http://crbug.com/106714, the placeholder thing is expected behavior. And what is wrong with your location.href? Do you have a test case? If that's a real bug, search for one on http://crbug.com and file and new one at http://new.crbug.com if none has been filed yet.
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 currently experiencing a very annoying problem with Google Chrome. I have some filters that are a multi-select and when I click to type on those filters, chrome suggests as an autofill option the placeholder for that select. I've never typed that text on this field, Chrome is getting that from the placeholder of the input.
Also, it seems that Google saved that placeholder as a "suggestion" to fill data on forms.
I've already tried to set those fields as autocomplete="off" and autocomplete="new-password and it did not work.
If I disable Chrome Option to autofill addresses, phone numbers and etc, this problem goes away.
I would like to be able to suppress chrome from suggesting this since it does not make any sense and makes using the filter a pain. I'm not sure if this is a chrome bug, a bug with select2, a combination of both. I've been looking everywhere on the internet to a solution and could not find one, does anybody know how to solve this?
To turn off the auto suggestions which are displayed in chrome try adding
<input autocomplete="off">
Even after adding this if chrome tries to give you auto suggestion, the most widely used technique is to add an hidden input field above your field to solve this problem
<input style="display:none" type="password" name="pass"/>
Adding this above input must solve the problem
Try to add another select2 with display="none", visibility="hidden" and autocomplete="off" before that one and see if the problem goes away.
Had this issue with a password input a while ago and that did the trick.
I have a very very weird bug. In Google Chrome everything is OK, only IE has this problem.
I use an AngularJS and ui-select component to create a multiple selects.
In IE, when I click into text input element, I can't type anything and even placeholder is not removed.
But when I click to URL address bar or click somewhere into DOM in Developer Tools (after hitting F12) first and then I click into that input, it normally works and I can write into input to filter options.
I tried a lot of with focus/blur, but nothing helps me. Please, did someone have similar problem?
Code:
Turns to:
I'm working with a contenteditable iframe that is being using for basic WYSIWYG editing. I've noticed a strange difference in the way that a Tab keypress event is handled between Chrome and Firefox.
When the document of the iframe has been configured using designMode = 'On', a tab pressed inside the document will skip to the next control in Firefox (expected) but create the following pre white-spaced span in Chrome
<span class="Apple-tab-span" style="white-space:pre"> </span>
Here's an example.
Interestingly, when the body of the iframe is setup instead using body.setAttribute("contenteditable", "true"), which I assumed was the same approach done in a different way, both browsers work as i would expect; moving the focus to the next tab index.
Can anyone explain why?
I'm afraid that the only answer is "just because". Don't expect that there's a reason behind how something works in contenteditable. I experienced hundreds of times that no one really cared or had time to care about that. When you've got bugs like https://code.google.com/p/chromium/issues/detail?id=226941 which make contenteditable totally irritating for users on Chrome & Opera and which hasn't been even confirmed by developers throughout entire year, then a small difference in Tab's behaviour is a detail which you have to fix and forget ;).
Use:
document.designMode = 'on';
Insted of
body.setAttribute("contenteditable", "true")
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