On Tue, Apr 4, 2017 at 8:12 PM, Ehsan Akhgari <ehsan.akhg...@gmail.com> wrote:
> I doubt it's used much. My assumption is only that not many sites are >> UA-sniffing Firefox, finding the <br>s, and modifying them in some way >> that breaks if they're no longer <br>s. That could still be totally >> wrong, though! >> > > Exactly. We can hypothesize either way, but we certainly can't know > easily without getting some data first. But unfortunately it's not > possible to collect data about what sites are doing in terms of DOM fix-ups > like this. We can, at least, collect data about whether they are > overriding the newline behavior wholesale though. Is there any reason why > we should not at least first collect this data before changing the behavior > here? > I agree that it doesn't seem likely that telemetry can answer this sort of question. However, we could collect data! Pick N top editing tools and actually test their behavior. We probably can't get full confidence, but we can get a much better picture of the risk involved. If we break (or significantly change behavior) on five sites out of 40, that's a strong indicator that we're going to have problems. As an example, have we already tested or is it in a plan to test: google docs basic and rich text editors on wikipedia office 365 github editor common rich text editor libraries, and common CRM software (I don't have a list) the top hosted email sites: gmail, yahoo, hotmail/outlook, aol, icloud, yandex Being able to assert, before landing this change, that it doesn't break any of these sites, would really help in terms of making assertions about the risk profile. --BDS _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
