Thank you in advance for reading my question.
As far as I know, document.domain setter in Chrome is supposed to be deprecated in M109
(The related link : https://developer.chrome.com/blog/immutable-document-domain/)
However, regarding links below, it seems like it's delayed to M110 or M111
(link 1 : https://chromestatus.com/feature/5428079583297536
link 2 : https://groups.google.com/a/chromium.org/g/blink-dev/c/nrLl0IxSxSI/m/FbWK4hIyAgAJ)
Does any one know since when Chrome doesn't support document.domain setter anymore?
ps. I tested document.domain setter in Chrome Canary which is version over M111, but it seemed still working.
In recent versions of Google Chrome, it is not possible to set the document.domain property. This has been the case since at least Chrome 73, which was released in March 2019.
Related
after multiple search, I can not find the answer, so I appeal to your knowledge. Since the last Chrome update on android, I can not use my gyroscope on virtual tours online anymore. My gyro includes my up and down motion but not right and left. Firefox is ok... Do you have more information?
Thx
It's a Chrome bug introduced in v65, as it appears from here bugs.chromium.org/. I'm using Chrome Beta to keep testing my work that uses the DeviceOrientation API since it works there. This also means that the bug will be fixed once the stable Chrome reaches v66 publicly.
Recently updated my Google Chrome to version 32.0.1700.76 m and it looks like tooltips have stopped appearing over html elements with the 'title' attribute set.
<span alt="Testing" title="Testing">hhh</span>
Here is an example jsFiddle:
http://jsfiddle.net/ricksuggs/cDhEL/
I thought it was an HTML standard, it is still working in Firefox, anyone else experiencing the issue?
Version 32.0.1700.76 m works fine for me. Have you tried just clearing your Chrome browser cache to make sure it's not a caching issue?
Unfortunately, this is an old bug that have pop with version 32.0.1700 and is still present in v55 on some system such as mine too.
If you encounter this bug. Please go to http://download1.srware.net/old/iron/win/portable to test version 31 then 32. If you find out it works with v31 but it doesn't with v32, please report it in the chromium bug tracker issue. Specify your setup sharing a link provided by DriversCloud.com to help dev to fix it. They need feedback and details.
I'm working on a project using KineticJS version 4.6 (currently the latest version), and since last night's Chrome update to Chrome 29, the Kinetic canvas is completely blank. While using the console, I am still able to detemine that the created objects, such as the Kinetic.Stage and Kinetic.Layer, still exist and are filled with correct data.
Afterwards, I tried loading the same page in Internet Explorer and Firefox, and they still work as intended, showing the canvas with the correct elements.
I have tried searching for people with similar issues, but I guess Chrome's update is too recent to show any results. Does anyone perhaps know if there is a way to fix it or if I should simply wait for either a KineticJS or a Chrome update?
EDIT: And now it suddenly works again after restarting Chrome. Hotfixed?
EDIT2: After a while it broke again, but restarting the browser seems to work
EDIT3: It is a bug in Chrome, acknowledged by the Chromium team in this thread. The thread states that the bug is definitely fixed in version 30, which is currently in beta. This fix may be merged in version 29 soon, but there is no definitive timetable for this.
We have the same problem in Chrome 29.
In some cases a workaround is to tell your users to use Chrome Incognito mode to fix this issue.
A test to replicate the issue consistently is posted here:
https://github.com/ericdrowell/KineticJS/issues/585
At present, the bug is not present in Chrome 30. (8/27/2013)
You should star this chromium issue:
https://code.google.com/p/chromium/issues/detail?id=280153
I just updated to the latest version of Chrome (17.0.963.56) and it appears that window.document.height is no longer a valid property. Has anyone else noticed this? I can't seem to find any documentation regarding it's removal.
After filing a bug with WebKit, I was informed that document.height
isn't a standard property and WebKit was the only vendor maintaining
support for it (until now.) Both MDN and WebKit now list the
properties as deprecated and suggest using
document.body.clientHeight or document.body.clientWidth instead of
document.width or document/height.
I had the same problem, window.innerHeight works for me.
docs here
I'm talking about the ability to provide a regular expression as the "pattern" attribute for an HTML textfield input. Like:
<input type="text" pattern="[abc]{3}"/>
According to http://www.chromium.org/developers/web-platform-status/forms, Chrome has supported this attribute for a while (not listed under any specific milestone). But according to http://www.coreservlets.com/html5-tutorial/input-types.html, this user tested the feature in Chrome 8 and it didn't work despite the official site claiming it should.
This feature seems to work fine in my version of Chrome, which is the latest version. However, I can't seem to find out which versions of Chrome this feature is supported in. The application I am working on is required to support Chrome versions as low as 6.0. So I wonder if someone can help me by letting me know what version of Chrome this feature was introduced?
PS: This feature definitely does not work in Safari at all. It's odd that it works in Chrome and not Safari as both are based on Webkit. This is even more evidence to me that it was probably only introduced in a fairly recent Chrome version.
It looks like has might have been supported since version 10.0.