New issue
Advanced search Search tips

Issue 608450 link

Starred by 2 users
Status: Available
Owner: ----
Cc:
editing-dev@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 3
Type: Bug



Sign in to add a comment

CTRL+A on a tag with contenteditable and mixed styling causes unexpected changes to tags and/or styling after typing

Reported by dennis.k...@gmail.com, May 2 2016 
Chrome Version       : Version 49.0.2623.112 m
URLs (if applicable) :
Other browsers tested: Firefox, Edge
  Add OK or FAIL, along with the version, after other browsers where you
have tested this issue:
    Firefox: OK, 48.0a2 (2016-05-01)
       Edge: OK, 25.10586.0.0

What steps will reproduce the problem?
(1) Have a tag with a contenteditable attribute with some content that is partly formatted, e.g: <strong>Hello</strong> World!
(2) Press CTRL+A (select all)
(3) Type something

What is the expected result?
Either replace everything with the typed content (like other browsers) or at least use the same tag/styling as before.

What happens instead?
Content that started with a <strong> tag gets replaced by content in a <b> tag.
Content that started with a <em> tag gets replaced by content in a <i> tag.
Content that used a font-size in pt gets replaced by content with a font-size in px (only seems to happen if the size differs from the default text size, otherwise it works correct and removes all content previously marked)

Please provide any additional information below. Attach a screenshot if
possible.
ce_styling.html
637 bytes View Download

Comment 1 by ssamanoori@chromium.org, May 4 2016

Components: Blink
Labels: M-52 OS-Linux OS-Mac OS-Windows
Status: Untriaged (was: Unconfirmed)
Able to reproduce the issue on Windows 7, Mac 10.10.5, Ubuntu 14.04 using 49.0.2623.112, latest stable 50.0.2661.94, canary 52.0.2724.0 with below steps:

1.Opened 'ce_styling.html' in chrome.
2.Pressed CTRL+A and typed something.
Observed that Content that started with a <strong> tag gets replaced by content in a <b> tag and content that started with a <em> tag gets replaced by content in a <i> tag.

Please find attached screencast.

This is non regression issue seen from M-30(30.0.1549.0).Hence, marking it as untriaged. Could anyone from dev team look into this issue please.
608450.mp4
442 KB Download

Comment 2 by cbiesin...@chromium.org, May 4 2016

Components: -Blink Blink>Editing

Comment 3 by yosin@chromium.org, May 11 2016

Components: -Blink>Editing Blink>Editing>Command
Status: Available (was: Untriaged)
Project Member

Comment 4 by sheriffbot@chromium.org, Jun 1 2016

Labels: -M-52 M-53 MovedFrom-52
Moving this nonessential bug to the next milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Project Member

Comment 5 by sheriffbot@chromium.org, Jul 11 2016

Labels: -M-53 MovedFrom-53
This issue has been moved once and is lower than Pri-1. Removing the milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Project Member

Comment 6 by sheriffbot@chromium.org, Aug 8 2017

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 7 by yosin@chromium.org, Aug 21 2017

Status: Available (was: Untriaged)
Project Member

Comment 8 by sheriffbot@chromium.org, Aug 21

Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 9 by yosin@chromium.org, Aug 28

Status: Available (was: Untriaged)
►

Sign in to add a comment