<p> not allowed in <h1> [contenteditable, execCommand, blink]
Reported by
cyril.au...@gmail.com,
May 6 2016
|
|||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2723.2 Safari/537.36 Steps to reproduce the problem: 1. https://jsfiddle.net/crl/1fw7m79w/ 2. https://jsfiddle.net/crl/1fw7m79w/1/ 3. What is the expected behavior? either <h1> or <p> should be removed (FF/gecko removes <h1>) What went wrong? invalid html Did this work before? N/A Chrome version: 52.0.2723.2 Channel: dev OS Version: 10.0 Flash Version: Shockwave Flash 22.0 r0 low importance, but just putting it
,
May 10 2016
here's the issue, in image
,
May 10 2016
Thank you for providing more feedback. Adding requester "brajkumar@chromium.org" for another review and adding "Needs-Review" label for tracking. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
May 18 2016
Able to reproduce the issue on windows 7, Linux Ubuntu 14.04 and Mac 10.11.5 using chrome version 50.0.2661.102 and canary 52.0.2739.2. Able to see both h1 and p tags in html as per the attached screen shot in comment #2. This issue is observed from M41 builds.the POSTS test is not displayed in Prior builds. Marking it as Untriaged to get more inputs from dev team. Thanks,
,
May 19 2016
,
May 20 2016
,
May 23 2016
same for <ol> and <ul>, they are not allowed in header tags: https://jsfiddle.net/crl/6skjxhb8/ <h1><ol><li>hello<br></li></ol></h1>
,
Jun 1 2016
Moving this nonessential bug to the next milestone. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 9 2016
"insertHTML" doesn't force validity of HTML for both inserted HTML and result HTML. It is due of web author to keep HTML valid. Since HTML5 doesn't have DTD, it is hard to validate it... |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by brajkumar@chromium.org
, May 10 2016Labels: Needs-Feedback
477 KB
477 KB Download