Created attachment 550011 [details] [diff] [review] backout patch I and smuag discussed this issue. Now all known regression bugs have patches. However, we need a big change for bug 671187 and bug 672181. Unfortunately, we don't have much time to test it in current cycle. Therefore, we decided that we backout the patches from Mozilla8. The attached patch backouts all changes. And it will be relanded after 8/16 (mozilla8 will be moved to Aurora). This bug manages the temporary backing out. I'll reopen bug 552707 and bug 644621. And I'll stay the state of all regression bugs. I need to keep to work on the regressions because the next cycle is shorter than current cycle and we have all hands meeting at mid September.
Do you want to back out before the Aurora merge, or back out from Aurora right after the merge?
(In reply to comment #1) > Do you want to back out before the Aurora merge, or back out from Aurora > right after the merge? Before. Because testers of nightly should test the backed out build.
Comment on attachment 550011 [details] [diff] [review] backout patch http://tbpl.mozilla.org/?tree=Tryfirstname.lastname@example.org&rev=751909a71c17
Comment on attachment 550011 [details] [diff] [review] backout patch In the commit message please add all the bug numbers this patch is backing out. Other option is to back out each bug individually. I think I'd prefer that. But either way rs=me
smaug: I'd like to reland the backed out patches with bug 671187 and bug 675614. Would you review them?
bug 672181 is a serious regression of the series of these bugs. It is especially reproduced with the patch for bug 644621 and <input> or <textarea> element since the size of them is typically small. I'm creating some patches which decelerate auto scroll speed in the bug. At least, we need to finish the bug before reland them. However, we might have selected wrong approach for bug 644621...