Status Update
Comments
ss...@google.com <ss...@google.com> #2
I notice the same issue and LogCat shows the following message:
Google Play services out of date. Requires 3159100 but found 3136130
Google Play services out of date. Requires 3159100 but found 3136130
di...@chromium.org <di...@chromium.org> #3
Same here.
"Google Play services out of date. Requires 3159100 but found 3136130"
"Google Play services out of date. Requires 3159100 but found 3136130"
pe...@google.com <pe...@google.com> #4
me as well....
Google Play services out of date. Requires 3159100 but found 3136130
Google Play services out of date. Requires 3159100 but found 3136130
ja...@chromium.org <ja...@chromium.org> #5
I was hopeful that the release of API 18 (4.3) would have created a solution to this, unfortunately it includes version 3158130
Description
NOTE: Changing the template (or component which causes a template change) may change the access level this bug defaults to and it may no longer be confidential.
Chrome Version: 133.0.6943.141 (Official Build) (64-bit) OS: Linux
What steps will reproduce the problem?
"[<b>hello</b>]"
)<div>
elementsinnerHTML
What is the expected result?
The DOM should render the nested text node between the 2 other text nodes (e.g. [hello]).
What happens instead?
The DOM renders altered HTML, moving the nested text node out from between the other text nodes (e.g. []hello).
This does not appear related to rendering since comparing the
innerHTML
value before and after shows the underlying HTML is different. Using the DOM API to create the nested structure does not run into hte same issue. See attached HTML file for an easy repro case. For what it's worth, I was able to repro the same issue in Firefox.Please use hotlists and text to provide additional information.
If this is a regression (i.e., worked before), please consider using the bisect tool (https://www.chromium.org/developers/bisect-builds-py ) to help us identify the root cause and more rapidly triage the issue.
For graphics-related bugs, please copy/paste the contents of the about://gpu page at the end of this report.
Upload Chrome variations which can help us investigate this issue. 1 Open Chrome. Go to chrome://version/?show-variations-cmd 2 Notice that there is a "Command-line variations" section(you might need to scroll down the page). Copy and save the value of the section to a txt file like variations.txt. 3 Upload the file to this bug as an attachment.