You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
on my live board and my test board (local), i have created a topic to explain all BBCodes (those included in this extension). The forums have this option "Enable quick reply" activated and Quickreply extension ( https://github.com/Tatiana5/QuickReply ) installed to display BBCodes on Quick reply.
When me or other user want to post a new message on this topic with Quick reply. During the posting, when we select a part of text and apply a BBCode, the view on windows up to some previous post.
I have test and it seems those next BBCodes are the cause if there are presents in a previous post (only one of these BBCode is enough to create this situation).
This is not an issue with this extension. If anything, it's a problem in that quick reply extension.
Even with ABBC3 disabled and removed, the issue is still there. Also, it happens with any bbcode if there is a marquee element on the page, but only when using that quick reply ext. This issue does not happen on the normal post reply page, for example, even though there are marquee elements displayed there too.
Hi,
on my live board and my test board (local), i have created a topic to explain all BBCodes (those included in this extension). The forums have this option "Enable quick reply" activated and Quickreply extension ( https://github.com/Tatiana5/QuickReply ) installed to display BBCodes on Quick reply.
When me or other user want to post a new message on this topic with Quick reply. During the posting, when we select a part of text and apply a BBCode, the view on windows up to some previous post.
I have test and it seems those next BBCodes are the cause if there are presents in a previous post (only one of these BBCode is enough to create this situation).
This "bug" is for Google Chrome 42, no problem with Firefox 37 and Internet Explorer 11.
The text was updated successfully, but these errors were encountered: