|
ppolymorphe wrote: All what look like a tag need to be Encoded to prevent nuke
Nearly.
What now happens is that all known tags that are forbidden are removed, but the child nodes of that tag are kept (previously they were nuked). Unknown tags (eg #include <stdio>) will be HTML encoded.
If the tags are in PRE blocks then everything is encoded.
cheers
Chris Maunder
|
|
|
|
|
Looks great
Patrice
“Everything should be made as simple as possible, but no simpler.” Albert Einstein
|
|
|
|
|
#include <stdio> now works as expected.
cheers
Chris Maunder
|
|
|
|
|
I pasted a url to a youtube video into a message and had the normal text added to make it a hyperlink. However, all the letters were made lowercase and for youtube that link becomes invalid.
For example, pasted link:
href="https://www.youtube.com/watch?v=vzl0qrsdy_o"
working link:
href="https://www.youtube.com/watch?v=VzL0qrSDy_o"
Chrome on Win10.
There are only 10 types of people in the world, those who understand binary and those who don't.
|
|
|
|
|
Oh FFS. In 2016.
(And yes I'm aware of the W3C's stand[^]: Quote: URLs in general are case-sensitive (with the exception of machine names). There may be URLs, or parts of URLs, where case doesn't matter, but identifying these may not be easy. Users should always consider that URLs are case-sensitive
My bad. I will fix this up and keep my swearing to a minimum.
(Though I challenge Google to give me a single reason why case sensitivity of URLs has a place in this day and age. grumble grumble grumble)
cheers
Chris Maunder
|
|
|
|
|
Chris Maunder wrote: Google to give me a single reason why case sensitivity of URLs has a place in this day and age.
It surprised me too. I suppose with so many videos this way they can reuse characters and get many more links out of the same alphabet.
There are only 10 types of people in the world, those who understand binary and those who don't.
|
|
|
|
|
Chris Maunder wrote:
(Though I challenge Google to give me a single reason why case sensitivity of URLs has a place in this day and age. grumble grumble grumble)
www.somesite.com/findexactstring?text=AbcXyz&caseSensitive=1
|
|
|
|
|
It you are writing a message, it used to work like this: type away, click the Bold widget, and <b></b> gets inserted, with the input position between the tags - so if you typed, the characters went inside the bold tag. Similarly, if you clicked Bold and then Italic, you got <b><i></i></b> with the input inside both tags.
Now, you click a widget and the tags are inserted, but the input goes to either the beginning or the end of the text box - I'm not sure exactly when it decides which, it's mostly the start, but I got a couple of ends writing this - means that text doesn't appear inside the tags, and Italic isn't inside Bold.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
I agree, it is annoying !
Hope it is fixed soon.
Patrice
“Everything should be made as simple as possible, but no simpler.” Albert Einstein
|
|
|
|
|
All fixed.
cheers
Chris Maunder
|
|
|
|
|
|
I extrapolate results when testing. 
cheers
Chris Maunder
|
|
|
|
|
Patrice
“Everything should be made as simple as possible, but no simpler.” Albert Einstein
|
|
|
|
|
When using the code button to add <pre> tags around a block of code, the page jumps back to the top rather than remaining positioned where the tags are inserted.
|
|
|
|
|
Should be good now.
cheers
Chris Maunder
|
|
|
|
|
It certainly is.
|
|
|
|
|
|
Fixed. Will deploy soon.
cheers
Chris Maunder
|
|
|
|
|
I could last week, but suddenly I can't remove email addresses and so forth in the forums.
Is this by design, or a recent bug?
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Addendum: I can't delete either.
This message: The Lounge[^] came up twice in moderation, so I had to let both through or confuse the automated system (and possibly give the OP a kick as a spammer, which he isn't)
And I can't delete either of them.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
But I can see only one message...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
There were two - it's possible the OP deleted one of them.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Bug or not, but I'm affected as well.
|
|
|
|
|
This will be back in a couple of hours.
Sorry about that: some maintenance (read: refactoring with extreme prejudice) has been going on and bits and pieces have been disconnected and plugged up while we address the bleeding.
cheers
Chris Maunder
|
|
|
|
|
Message Removed
modified 8-Oct-16 22:37pm.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
