In Q&A, TextBox messing user input.
-
In Q&A and probably in other places, TextBoxes (including comments) are changing user input on their own. - During user input/edition, preview look good. - When 'Submit you question' is hit, a process alter user input.
// because of '< ' anything goes well
for(int i=0; i< n; i++) {
a += i;
}// because of '<n' anything after it gets lost
for(int i=0; i<n; i++) {
a += i;
}// if there is '<n' 2 times, everything in between is messed
for(int i=0; i<n; i++) {
a += i;
}
for(int i=0; i<n; i++) {
a += i;
}Encoding the input prevent problems. My understanding: As soon '<n' is encountered, process recognize as beginning of xml/html tag and remove anything after it if there is only 1. If there is 2 '<n', anything in between gets altered with some '=""' inserted between words. I think it would be more natural if the feature was deactivated by default I am sure I already reported same thing, but unable to find it in forum history.
Patrice “Everything should be made as simple as possible, but no simpler.” Albert Einstein
-
In Q&A and probably in other places, TextBoxes (including comments) are changing user input on their own. - During user input/edition, preview look good. - When 'Submit you question' is hit, a process alter user input.
// because of '< ' anything goes well
for(int i=0; i< n; i++) {
a += i;
}// because of '<n' anything after it gets lost
for(int i=0; i<n; i++) {
a += i;
}// if there is '<n' 2 times, everything in between is messed
for(int i=0; i<n; i++) {
a += i;
}
for(int i=0; i<n; i++) {
a += i;
}Encoding the input prevent problems. My understanding: As soon '<n' is encountered, process recognize as beginning of xml/html tag and remove anything after it if there is only 1. If there is 2 '<n', anything in between gets altered with some '=""' inserted between words. I think it would be more natural if the feature was deactivated by default I am sure I already reported same thing, but unable to find it in forum history.
Patrice “Everything should be made as simple as possible, but no simpler.” Albert Einstein
When you don't put a space before and after a binary operator, this is what happens. Cruel but fair. :laugh:
Robust Services Core | Software Techniques for Lemmings | Articles
The fox knows many things, but the hedgehog knows one big thing. -
When you don't put a space before and after a binary operator, this is what happens. Cruel but fair. :laugh:
Robust Services Core | Software Techniques for Lemmings | Articles
The fox knows many things, but the hedgehog knows one big thing. -
In Q&A and probably in other places, TextBoxes (including comments) are changing user input on their own. - During user input/edition, preview look good. - When 'Submit you question' is hit, a process alter user input.
// because of '< ' anything goes well
for(int i=0; i< n; i++) {
a += i;
}// because of '<n' anything after it gets lost
for(int i=0; i<n; i++) {
a += i;
}// if there is '<n' 2 times, everything in between is messed
for(int i=0; i<n; i++) {
a += i;
}
for(int i=0; i<n; i++) {
a += i;
}Encoding the input prevent problems. My understanding: As soon '<n' is encountered, process recognize as beginning of xml/html tag and remove anything after it if there is only 1. If there is 2 '<n', anything in between gets altered with some '=""' inserted between words. I think it would be more natural if the feature was deactivated by default I am sure I already reported same thing, but unable to find it in forum history.
Patrice “Everything should be made as simple as possible, but no simpler.” Albert Einstein
I will take a look at this.
"Time flies like an arrow. Fruit flies like a banana."
-
I will take a look at this.
"Time flies like an arrow. Fruit flies like a banana."
Thank you. you can see problem in this question, OP just forgot to use the <pre> tag. How can I change this code to solve n equation? .[^] Would be nice to be able to block the changing process.
Patrice “Everything should be made as simple as possible, but no simpler.” Albert Einstein
-
In Q&A and probably in other places, TextBoxes (including comments) are changing user input on their own. - During user input/edition, preview look good. - When 'Submit you question' is hit, a process alter user input.
// because of '< ' anything goes well
for(int i=0; i< n; i++) {
a += i;
}// because of '<n' anything after it gets lost
for(int i=0; i<n; i++) {
a += i;
}// if there is '<n' 2 times, everything in between is messed
for(int i=0; i<n; i++) {
a += i;
}
for(int i=0; i<n; i++) {
a += i;
}Encoding the input prevent problems. My understanding: As soon '<n' is encountered, process recognize as beginning of xml/html tag and remove anything after it if there is only 1. If there is 2 '<n', anything in between gets altered with some '=""' inserted between words. I think it would be more natural if the feature was deactivated by default I am sure I already reported same thing, but unable to find it in forum history.
Patrice “Everything should be made as simple as possible, but no simpler.” Albert Einstein
I can't seem to replicate the issue.
// if there is '
// because of '
In QA and forums this seems to work OK.
In the QA you linked to, the code block wasn't enclosed in PRE, so it was treated as raw HTML. The <n was considered by our HTML cleaner as the start of a tag and it tried to correct it. It's kinda hard to fix issues like this because it could have easily been <i, which could legitimately been a mal-formed italic tag.
Best solution: make new users use Markdown. Still, it has it's own quirks...
cheers
Chris Maunder -
I can't seem to replicate the issue.
// if there is '
// because of '
In QA and forums this seems to work OK.
In the QA you linked to, the code block wasn't enclosed in PRE, so it was treated as raw HTML. The <n was considered by our HTML cleaner as the start of a tag and it tried to correct it. It's kinda hard to fix issues like this because it could have easily been <i, which could legitimately been a mal-formed italic tag.
Best solution: make new users use Markdown. Still, it has it's own quirks...
cheers
Chris Maunder -
I can't seem to replicate the issue.
// if there is '
// because of '
In QA and forums this seems to work OK.
In the QA you linked to, the code block wasn't enclosed in PRE, so it was treated as raw HTML. The <n was considered by our HTML cleaner as the start of a tag and it tried to correct it. It's kinda hard to fix issues like this because it could have easily been <i, which could legitimately been a mal-formed italic tag.
Best solution: make new users use Markdown. Still, it has it's own quirks...
cheers
Chris Maunder
