Get a better browser then; Chrome's had it built in for ages. :P
Re: New revs
« Reply #240, on October 12th, 2010, 02:51 PM »
Get a better browser then; Chrome's had it built in for ages. :P
Get a better browser then; Chrome's had it built in for ages. :P
Well... UTF-8 is one form of Unicode. The whole concept is a total mess anyway -sigh-. Anyway, the idea is that it should always be valid UTF-8 (and by proxy valid Unicode) except that in some cases it isn't, but I have no idea why that might be. It's been there since 1.1, and it may not be relevant any more - doubly so since it never seemed to be called before.
What was happening is that there was an extra output buffer existing that shouldn't have existed, which was causing content not to be flushed properly - and even if it did get flushed, the result would be corrupted because it would be gzipped content when the header implied otherwise. (I haven't checked the browser-specific stuff yet, that's next up)
I wonder why SMF never did that.Quote unset($GLOBALS['cachedir'], $GLOBALS['db_character_set']);
// Characters we just shouldn't allow, regardless.
foreach (array('*') as $char)
if (strpos($checkName, $char) !== false)
if ($fatal)
fatal_lang_error('username_reserved', 'password', array($char));
else
return true;
It still breaks though, vomiting raw JS onto the page :/
Not only that but we've made some very large changes to the codebase, and it's unlikely we'd have totally caught every one first time simply because they are very large changes with lots of consequences.
Yeah, I remember that... Damn you, Google fanboys!
Let's just say they didn't know unset() could be called with multiple parameters.
Just like in Subs-Members.php... I see no other reason to use THAT, and even the comment spells it out. 'Characters'. (Feel free to delete it.)
Not only that, but you have no idea how fun it's going to be when I get to update to the latest SMF SVN...
I thought I remembered seeing Opera have a resizeable textarea a year or more ago?Quote Yeah, I remember that... Damn you, Google fanboys!
Then again that would have been during my Star Pirates/Greasemonkey days where I was fudging GM to work on Firefox, Opera, Safari with SIMBL support (thanks to Asgard), so I sorta lost track of what did what.
I bet once upon a time there were more characters in that list, or should have been.
As I keep trying to tell Antechinus, spending time farting around with stupid little changes in the source that doesn't benefit anyone just slows down actually fixing real issues.
! Removed random support for Firefox and Opera in downloads, they work just fine with the default, even with filenames with UTF-8 in them. (Download.php)
! Another silly bugfix from the UTF-8 stuff. (Subs-Post.php)
That's what you get when code stays static for years!
Did you test with older but still supported versions of Opera and FF? I can test with Opera 9 if you ask me.
Can't we just remove the first parameter? It'll always be set to UTF-8 anyway...
Get a better browser then; Chrome's had it built in for ages. :PQuote Okay, I'll switch to the post editor... Quick Reply is cool when you're not replying to a long post. There's no handle to increase its size... (Idea for later.)
I just wanted it to work without spewing errors for registrations so I could sign up test accounts for attachment testing.
I just had the account sign up regularly, which causes an email, and the email functions still had $charset in them without $charset being defined.