HTML parsing issues in Firefox
#1
HTML parsing issues in Firefox
Lately I am seeing issues with the html parser for post composing posts in VBulletin using Firefox. I took a while to report it because I am not sure what is causing it. The most troublesome aspect of the issue is vBulletin does not allow breaks to be inserted in posts without manually inserting them in html. It used to allow that. You can't just hit enter any more and get your line break. I debated whether maybe that was intentional for some purpose like saving web space, but I doubt it now. It is a new issue. The html parser should generate the typical br wrapped with carrots when you hit enter, which it is not doing for some reason. It will parse or recognize them if the user puts them in manually.
The second thing it does now that I have noticed is parse quotations incorrectly after the initial save is re-worked. For example, if you insert quotes around some text in a post, save it, then reopen the post to re-edit, the parser swaps the quotes for a string of symbols which are nonsensical. It then cannot parse its own nonsensical symbology. It is a string of symbols with seemingly random ampersands, percent signs, and hash marks thrown in the line. The system needs to be able to generate correct html coding and allow subsequent editing without disturbing the initial coding.
The second thing it does now that I have noticed is parse quotations incorrectly after the initial save is re-worked. For example, if you insert quotes around some text in a post, save it, then reopen the post to re-edit, the parser swaps the quotes for a string of symbols which are nonsensical. It then cannot parse its own nonsensical symbology. It is a string of symbols with seemingly random ampersands, percent signs, and hash marks thrown in the line. The system needs to be able to generate correct html coding and allow subsequent editing without disturbing the initial coding.
Last edited by Cubdriver; 10-25-2014 at 08:48 AM.
#2
Gets Weekends Off
Joined APC: Sep 2013
Position: Good Ship Lollipop
Posts: 401
Lately I am seeing issues with the html parser for post composing posts in VBulletin using Firefox. I took a while to report it because I am not sure what is causing it. The most troublesome aspect of the issue is vBulletin does not allow breaks to be inserted in posts without manually inserting them in html. It used to allow that. You can't just hit enter any more and get your line break. I debated whether maybe that was intentional for some purpose like saving web space, but I doubt it now. It is a new issue. The html parser should generate the typical br wrapped with carrots when you hit enter, which it is not doing for some reason. It will parse or recognize them if the user puts them in manually.
The second thing it does now that I have noticed is parse quotations incorrectly after the initial save is re-worked. For example, if you insert quotes around some text in a post, save it, then reopen the post to re-edit, the parser swaps the quotes for a string of symbols which are nonsensical. It then cannot parse its own nonsensical symbology. It is a string of symbols with seemingly random ampersands, percent signs, and hash marks thrown in the line. The system needs to be able to generate correct html coding and allow subsequent editing without disturbing the initial coding.
The second thing it does now that I have noticed is parse quotations incorrectly after the initial save is re-worked. For example, if you insert quotes around some text in a post, save it, then reopen the post to re-edit, the parser swaps the quotes for a string of symbols which are nonsensical. It then cannot parse its own nonsensical symbology. It is a string of symbols with seemingly random ampersands, percent signs, and hash marks thrown in the line. The system needs to be able to generate correct html coding and allow subsequent editing without disturbing the initial coding.
Firefox recently released a software update. Are you running this latest version?
Alternately, have you cleared the cookies for APC recently to see if that has any effect?
#4
Gets Weekends Off
Joined APC: Sep 2013
Position: Good Ship Lollipop
Posts: 401
#5
Nope, I updated to Firefox 33 and it is still doing all the same incorrect html behaviors, plus a few more, and below is an example of the system leaving html code snippets that should have been parsed (below).
It is also doing some other things in addition. The little yellow insert image icon does not function, nor does the dropdown menu list appearing under a user name. Used to be you could click on a username and get a drop down of things to see like find all posts by this user and so on.
I'll install Chrome and see what happens.
It is also doing some other things in addition. The little yellow insert image icon does not function, nor does the dropdown menu list appearing under a user name. Used to be you could click on a username and get a drop down of things to see like find all posts by this user and so on.
I'll install Chrome and see what happens.
#6
Gets Weekends Off
Joined APC: Sep 2013
Position: Good Ship Lollipop
Posts: 401
Nope, I updated to Firefox 33 and it is still doing all the same incorrect html behaviors, plus a few more, and below is an example of the system leaving html code snippets that should have been parsed (below).
It is also doing some other things in addition. The little yellow insert image icon does not function, nor does the dropdown menu list appearing under a user name. Used to be you could click on a username and get a drop down of things to see like find all posts by this user and so on.
I'll install Chrome and see what happens.
It is also doing some other things in addition. The little yellow insert image icon does not function, nor does the dropdown menu list appearing under a user name. Used to be you could click on a username and get a drop down of things to see like find all posts by this user and so on.
I'll install Chrome and see what happens.
That is pretty weird! Thanks for the screenshot, that also helps.
If the same thing is happening on Chrome then it's likely a bug that our techs will have to look into.
#7
Brandi you'll be relieved to know it's Firefox that's doing it. Google Chrome does not do the same things. Oddly enough, GC has some other issues that are not as serious, it fails to run many of the little toolbar icons in post-composer for example.
Thread
Thread Starter
Forum
Replies
Last Post