Bug 1449255: Part 4a - Rename test_bug393285 to test_blocklist_osabi.js and modernize. r=aswan MozReview-Commit-ID: FPdc1y88ZXu

Bug 1449255: Part 3b - Cleanup update URL parameter interpolation. r=aswan MozReview-Commit-ID: FTLC5WFGYj7

Bug 1449255: Part 3a - Delete test_bug384052 and the functionality it tests. r=aswan This is all dead code now that legacy extensions are gone. WebExtensions have no way to implement this. MozReview-Commit-ID: IDoH6HATKcc

Bug 1449255: Part 2 - Fold test_bug371495 into test_manifest. r=aswan MozReview-Commit-ID: 69LtwXgwBT0

Bug 1449255: Part 1 - Fold test_bug335238 into test_update. r=aswan MozReview-Commit-ID: KLODBGSOR37

Bug 1451562 - Update pdf.js to version 2.0.480. r=bdahl

Bug 1450162. Correctly merge in the presence of reorderings. r=mstange Previously we were assuming that we'd always get the display list in a canonical ordering. With retained display lists this assumption is false.

Bug 1293445 - 5 - Rename RESULTS_AS_TAG_QUERY. r=standard8 MozReview-Commit-ID: 7HwPKkGvAvv

Bug 1293445 - 4 - Remove RESULTS_AS_TAG_CONTENTS. r=standard8 MozReview-Commit-ID: rybSCGrfnf

Bug 1025724 - Add some shadow tree style tests. r?bz MozReview-Commit-ID: 3d9ewWoM8Mo

Bug 1444301 - Add spacing around separator at end of toolbox; r?jryans MozReview-Commit-ID: 2Dkiu1MHGBj

Bug 1444301 - Fix badly rounded corner on frames graphic; r?jryans There seems to be a bug in the way the top-right corner of the frames graphic is rounded. This patch fixes it to make it consistent with the other corners. MozReview-Commit-ID: I7z5IVcEZHL

Bug 1444301 - Make the meatball button a little less meaty; r?jryans This patch also reworks the SVG to make it a little easier to adjust in future. MozReview-Commit-ID: 7R3hDL3qaVD

Bug 1444301 - Tweak RDM button; r?jryans In the mockup the RDM button is slightly fatter than the current button. This patch adjusts the width of the button, tidying up the file at the same time as follows: * Move the contents to the center (it was off to the right by 0.5px) * Use relative paths for the SVG to make it easier to adjust in future * Fix some precision issues with paths not quite lining up * Simplify the SVG path data MozReview-Commit-ID: KAyx9Ki4y47

Bug 1444301 - Adjust spacing of iframe button; r?jryans This button is a little unbalanced: the icon is in the middle of the button but the drop-down arrow is flush up against the side. Now that it appears right before the separator it looks quite odd since the arrow is touching the separator. This patch adjusts the margins so that the contents sit more neatly inside the button. This patch also fixes the vertical position of the arrow so that it is a little lower, to match the mockup. MozReview-Commit-ID: 3P50X69paFb

Bug 1447544 - Remove the event listeners and timers when the videocontrols binding is destroyed Additionally, - Remove `self = this` usage - Access to the `Utils` object from the scope chain MozReview-Commit-ID: 5kbLgD951CM

Bug 1447544 - Set firstShow to false before the control fades out The flag is used to trigger play() when the control first hides. There is no reason to set only after transition ends. We can set it to false as soon as we trigger play(). This is likely to fix a regression from bug 1449532 given that we have switched to Web Animation API there. MozReview-Commit-ID: F4n3rKdzYKr

Bug 1449564 - part 3: Make absolute position editor listen to mouse events at the system event group r?m_kato Currently, absolute position editor listens to mouse events at the default event group to handle dragging of positioner. However, this is blocked by a call of Event.stopPropagation() in web apps unexpectedly. Therefore, we should make it listen to the events at the system event group instead. MozReview-Commit-ID: Hoa8c9QvMuG

Bug 1449564 - part 2: Make absolute positioned element editor disabled in default and make it possible to enable it with new command r?m_kato, smaug We have another built-in UI of editor which is not implemented by any other browsers. That is a draggable handler to move absolute positioned elements. So, we should disable it in default for compatibility with the other browsers. However, different from resizers and inline table editor, we don't have command to enable/disable this feature but for backward compatibility, we should have it. Therefore, this patch adds new command "enableAbsolutePositionEditor". Note that whether resizing UI is available only with enableObjectResizing state is different from enableInlineTableEditing command. Resizers for absolute positioned elements are NOT available both enableObjectResizing and enableAbsolutePositionEditor are enabled. Additionally, this adds automated tests to check basic functions of absolute positioned editor. MozReview-Commit-ID: 9ZSGB8tLpFw

Bug 1449564 - part 1: Disable object resizer and inline table editor in default r?m_kato Gecko supports resizers of <img> elements and <table>, <td>, <th> elements and has UI to remove existing table row or column in default. However, the other browsers don't have such UI and web apps need to disable this feature with calling both: document.execCommand("enableObjectResizing", false, false); document.execCommand("enableInlineTableEditing", false, false); for avoiding conflicting with their own features to edit such elements. Therefore, it doesn't make sense to keep enabling them in default only on Gecko. If web apps want to keep using these features, they should call: document.execCommand("enableObjectResizing", false, true); document.execCommand("enableInlineTableEditing", false, true); at initializing the editor. And also this patch fixes bugs of document.queryCommandState("enableObjectResizing") and document.queryCommandState("enableInlineTableEditing"). They always return false even after calling document.execCommand(..., false, true) since nsSetDocumentStateCommand::GetCommandStateParams() sets bool value as STATE_ATTRIBUTE. However, nsHTMLDocument::QueryCommandValue() which is the caller referring STATE_ATTRIBUTE doesn't treat it as bool value. And also those commands are related to state of document. Therefore, they should be return as bool value of STATE_ALL instead. Then, nsHTMLDocument::QueryCommandState() returns the state as expected. Note that those commands are supported only by Gecko. So, we don't need to worry about the compatibility. Finally, this patch rewrites 2 existing tests to check basic behavior of resizers and appearance of resizers. Note that this patch does not add new tests to test inline table editor since it's difficult to test the behavior with current API. Perhaps, we should add an API to nsIHTMLEditor to retrieve each anonymous elements in another bug since it requires to add wrapping API of SpecialPowers. MozReview-Commit-ID: 1FhYo5vcV60