[Update] Issues with Replying to Topics on Firefox and Brave Browser

[AlTech]

15 minutes ago, colonel_mortis said:

Thanks. The first one with the mangled stuff is very definitely not supposed to look like that. Can you try clearing your cache, then see if it looks more normal (and the editor works) after that?

The editor works now but I'm not sure if it'll go back to not working.

 

Edit: Here's the thing again but this time working

 

Quote

CKEDITOR.plugins.add("ipssource",{init:function(b){b.on("instanceReady",function(a){this.dataProcessor.writer.selfClosingEnd="\x3e";a=CKEDITOR.dtd;for(var b in CKEDITOR.tools.extend({},a.$nonBodyContent,a.$block,a.$listItem,a.$tableContent))this.dataProcessor.writer.setRules(b,{indent:!0,breakBeforeOpen:!0,breakAfterOpen:!0,breakBeforeClose:!0,breakAfterClose:!0})});b.on("mode",function(a){$(window).trigger("resize")})}});

 

 

[colonel_mortis]

23 minutes ago, AluminiumTech said:

The editor works now but I'm not sure if it'll go back to not working.

 

Edit: Here's the thing again but this time working

 

 

That looks more like what I was expecting. If it stops working again, please let me know.

[AlTech]

On 22/07/2018 at 1:32 PM, colonel_mortis said:

That looks more like what I was expecting. If it stops working again, please let me know.

It happened again.

 

Here's the info:

 

 

Hovering over the plugin shows "ipspaste" in the URL.

 

Quote

CKEDITOR.plugins.add("ipssource",{init:function(b){b.on("instanceReady",function(a){this.dataProcessor.writer.selfClosingEnd="\x3e";a=CKEDITOR.dtd;for(var b in CKEDITOR.tools.extend({},a.$nonBodyContent,a.$block,a.$listItem,a.$tableContent))this.dataProcessor.writer.setRules(b,{indent:!0,breakBeforeOpen:!0,breakAfterOpen:!0,breakBeforeClose:!0,breakAfterClose:!0})});b.on("mode",function(a){$(window).trigger("resize")})}});

 

 

[colonel_mortis]

2 hours ago, AluminiumTech said:

It happened again.

 

Here's the info:

 

 

Hovering over the plugin shows "ipspaste" in the URL.

 

 

That is almost certainly a different issue to the previous one. It's complaining that a read-only property that should definitely exist actually doesn't, which suggests to me that perhaps it's being caused by a conflict with a browser extension or something. Does it happen with addons disabled?