Useless FONT style="vertical-align:inherit" is inserted
Reported by
luzar.da...@gmail.com,
Mar 19 2018
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.162 Safari/537.36 Steps to reproduce the problem: Sometimes (cannot reliably reproduce) on DOM inserts, chrome surrounds random DOM elements with superfluous <font> tags. I have no real idea how to reproduce this. It happens seemingly on random, but at the same time it usually happens to a certain subset of DOM modifications (i.e., I noticed it happening to a particular part of our application. But it also happens in completely unrelated parts, such as CodeMirror text editor, so it's not related to our app, per se). I realize my description is totally unhelpful in diagnosing this issue, but I'm completely at loss and was hoping someone having similar problems could shed more light. The font tags are *always* containing: <font style="vertical-align: inherit;"> ... </font> What is the expected behavior? What went wrong? It's causing real problems, ranging from extra whitespace around DOM elements, to inability to use the app at all (when it's happening inside the CodeMirror editor, it becomes unusable). Started happening around v65 (maybe v64, but not sure). Did this work before? N/A Does this work in other browsers? Yes Chrome version: 65.0.3325.162 Channel: stable OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version:
,
Mar 19 2018
,
Mar 20 2018
Is this happened by typing keyboard or insert link? I could not reproduce this behavior thus we need to have small reproduce case. I agree that we should not insert useless FONT style="vertical-align:inherit".
,
Mar 20 2018
I'd say it happens when inserting into DOM (via `.innerHTML` etc.). WTBS, something obvious I have not considered is it could be caused by some extension. I forgot to consider this because it happened to at least two people, but it turns out we have overlapping extensions. But mainly, it just didn't cross my mind -- would be cool if the crbug form reminded people to ensure they have all extensions disabled before issuing :). Thus, let's freeze this issue until I'm able to either confirm/reject this hypothesis (it could take a while since that bug really manifests itself as it pleases).
,
May 5 2018
Haven't reproduced since then. So it might have been some extension that was meanwhile updated, after I re-enabled all. Issue can be closed. |
|||
►
Sign in to add a comment |
|||
Comment 1 by f...@opera.com
, Mar 19 2018