Created attachment 525061[details][diff][review]
Removed nsIHTMLEditRules and made the methods member of nsHTMLEditRules
This is my first patch with use of the queue, so I hope all went fine. I´m not sure about the "former nsIHTMLEditRules methods" comments, but I thought it could be useful.

Created attachment 527927[details][diff][review]
Removed nsIHTMLEditRules and made the methods member of nsHTMLEditRules
If I hadn´t messed up with the queue again, it should work fine now. I had took a look over it and couldn´t see something missing now.
I hope I´m right. :)

No I had now tried to, but it doesn´t worked. I have found this guide here https://wiki.mozilla.org/ReleaseEngineering/TryServer, but I´ve got everytime a error message from Putty: "No supported authentication methods available"
The last command at this site (with the -e ...) isn´t even recognized as valid command at all. I´m using TortoiseHG, maybe this is the problem? (And is it okay to ask here? Else I will ask per e-mail next time)
Anyway, thank you :)

I've never used putty with tortoisehg myself (I use the hg command from the terminal!), but looking at http://row1.info/news/91-blog/265-using-tortoisehg-with-bitbucket-and-ssh.html, it seems that you need a line like this in your mercurial.ini file:
ssh = "C:\Program Files (x86)\TortoiseHg\TortoisePlink.exe" -ssh -2 -i C:\Users\YourUsername\.ssh\yourkey.ppk
Also, make sure that your LDAP user name in the URL.
If that doesn't work out, you can always use the command line. In order to do that, you should export your SSH key from putty into the OpenSSH format, put it in ~/.ssh/.id_rsa (private key) and ~/.ssh/.id_rsa.pub (public key), and modify ~/.ssh/config like this: <https://developer.mozilla.org/en/Creating_Mercurial_User_Repositories#Configuring_ssh>, and push to try using hg push -f ssh://hg.mozilla.org/try. That configuration is guaranteed to work. :-)
Let me know if you can't get it to work.

The non-android reftests are a known intermittent orange. Jetpack failures are expected, I believe. Android browser-chrome failures are expected. Android Mochitest 2 looks like an infra or harness failure. Android R2 looks like the same. The mobile folks tell me that the failing Android R1 tests are nothing to worry about either. I think you're clear!