Loading Profile...
Problem handling less-than sign in bug submission text field
Hi,
I ran into a bug with the very field I'm typing this into right now (the textarea element).
I was submitting a bug report to a developer and it was botching up when I put a less-than sign into the text (<). Using an "&" + "lt;" works just fine for making less-than signs, but you're apparently not parsing the text and doing a simple substitution before displaying it... most likely a simple oversight, but very annoying =P
I ran into a bug with the very field I'm typing this into right now (the textarea element).
I was submitting a bug report to a developer and it was botching up when I put a less-than sign into the text (<). Using an "&" + "lt;" works just fine for making less-than signs, but you're apparently not parsing the text and doing a simple substitution before displaying it... most likely a simple oversight, but very annoying =P
I’m annoyed
1 person has this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
-
Inappropriate?botching up in what way? If you could give me details about the behavior It would really help me track down what is going on.
The only thing you should have to be careful of is putting html tags in your text. Things like <script> and such. We have to strip those out because if we don't, malicious users can use that to ruin people's experience on the site or steal their information.
Could you email the text that was screwing up to me at scott@getsatisfaction.com?
I’m sorry it didn't work
-
Inappropriate?Here's the text I entered and had trouble with... I'll put it in the comments here so you can see it in action in the system:
__________________________
I was updating my SSBs and ran into this little bug consistently for every SSB that had multiple tabs open:
Series of events:
- Open old SSB version
- Automatic alert of update (very nice new version, by the way)
- Download and install
- Relaunching application
- Receive dialog alerting me to the fact that I have multiple tabs open and asking me if I wish to proceed (normal behavior)
- Click "Close" button (everything is fine and dandy so far)
- SSB quits
- First SSB launch (<----> are set by default. Kudos =) -
Inappropriate?Here is the same text, only I've replaced the angle-bracket with the html code æ&" + "lt;"
________________________________
I was updating my SSBs and ran into this little bug consistently for every SSB that had multiple tabs open:
Series of events:
- Open old SSB version
- Automatic alert of update (very nice new version, by the way)
- Download and install
- Relaunching application
- Receive dialog alerting me to the fact that I have multiple tabs open and asking me if I wish to proceed (normal behavior)
- Click "Close" button (everything is fine and dandy so far)
- SSB quits
- First SSB launch (<-----this throws an error when it tries to close itself automatically)
- Second SSB launch
The error I'm encountering is this: http://img.skitch.com/20080626-2cdb3k...
In addition to the error dialog, it is displaying the normal "multiple tabs open" alert dialog, so I'm guessing that somehow the "first relaunch" of the SSB encounters that when it tries to close itself and doesn't know what to do with those extra tabs.
("Picture 5.png" in the sidebar of Preview shows the two icons side by side in the dock. I did not encounter any problems aside from the fact that the first "SSB" didn't know what to do with multiple tabs when it tried to quit itself).
Let me know if I need to explain better. This whole thing isn't really a big deal, and you may already know all about it, but I thought I'd let you know anyways.
Awesome work on the update! (I'm especially fond of the fact that "Block Popups" and "Only Accept Cookies..." are set by default. Kudos =) -
Inappropriate?As you can see.... the first one clipped the text and is apparently adding the greater-than as it seems to think it needs to complete the html tag somehow. Interesting bug.
EMPLOYEE
