Wedge

Wedge is European. We don't have problems with language :P

Have you tried turning it off and on again?™

Have you tried turning off gzipping?

Is this the default php.ini in WampServer? (The one in the Apache bin folder.)

Actually, come to think of it... It might very well have been.
After all, some of the devs did the transition quite... reluctantly.It's this way. <----
Unless you're looking from inside my monitor, of course. (Now get off my monitor!)Yeah, but $scripturl is a special one... Many of its uses aren't easily portable to <URL>. So we're trying to do it carefully. There are still over 1500 uses of it throughout the source... Oh my, I never realized.

Oh, makes me think... I think somewhere else you asked about making ob_sessrewrite callable from a non-buffer context so that we could apply pretty URLs and <URL> transforms to any string, without having to bother with resetting the buffer output. Is it still in the news..? I know I wanted to do that 'back in the day', but I can't remember why I stepped back, though.

I know, I was just pulling your leg :P Twice even :^^;:

Oh, right, you probably weren't there at the time SMF underwent the {change}. That was in late 2007 or early 2008... Charter members and beta testers with access to the files were disgusted at how the team had implemented the security change -- while it was a GOOD thing, it was done in such an automated way, we'd find many useless escaped strings and it really, really made the codebase look so ugly... Over the months, though, the devs ensured that the initial mess was mostly cleaned up, but they still left a lot of {int:zero} things here and there...
Of course, there's one case where it's all right to use this system for constants. Which is explaining an integer value of an option list. For instance, SELECT something WHERE value IN ({int:nobody}, {int:everyone}) -> array('nobody' => 0, 'everyone' => 1).
In this case, yes, it's better to stick with the escaped constant.

Anyway: sorry if my sarcasm wasn't too obvious. Maybe it's the lack of sleep... Only had less than 3 hours today.

But posting this thing in the changelog sort of made me consider removing the 'obvious' ones.
Well, I guess I'll do that... When I see them!
I already spent half an hour turning strings to literal this morning, so I guess I'll leave it for another time.
Do you want to do the rest by yourself, BTW..? I think I did at least half of them.

Again, you should PM me or bump multiple times when you want to catch my attention. As I said before, there are too many topics and I try to focus on development rather than development discussion (since I haven't found the magic formula that allows me to do both and also deal with real life...), anyway.

I'm afraid I don't like these alternatives. The second one is better but overall its font is only supposed to remind you of 'new' posts, so a number in that style would represent a post number, not a page number... I know, it's only very technical, but I certainly don't get why the 'next' and 'go down' links should be using the same font, too...

I'd suggest doing the same styling, but only for the numbers area. Do you want me to make a mockup or something...?

@godboko> Fat fingers should use Chrome for Android. It actually detects fat fingers and does a 'pop-up zoom' of the area you clicked, so that you can do a proper choice... I love how intuitive that one is. And, of course, iOS and Android Stock Browser don't have it... -_-

It could be argued that Likes also use the same styling for numbers, so I'll try to think of it that way.

I've done various tests, and found one that I like enough.
It's done on the basis that only the numbers are styles. But the 'trick', is that you get the current page to be shown either on a green, or red background. The difference..? Green = it's all done. Red = there's new stuff to be found on this page.
I think it works well, but then another problem occurs to me: is it worth keeping the 'new' indicator next to later pages..? Just a simple example: let's say you've read all 3 pages of a topic... Then you go back to page 1, but in the meantime, someone posted in page 3. In the current Wedge, you'll see a New indicator in the page list. In the proposed change, you'll just see a green page number, and that's all.

And as you can see, I immediately adopted it... ;D

I think the best way to ensure it's used everywhere, is to do it the hard way, i.e. search for {string: and verify what it's matched to... Also, as I asked in the changelog: should we do {literal:0} things, too..?

rev 1950 -- I'm hungry... Can't sleep... Browsing on my S3... Fixing stuff for it.
(2 files, 2kb)

! Fixed scrollbar no longer being reactive in Android. This was mostly due to the fact that I forgot the window object has a scrollTo method already. Costs an additional 2 bytes to fix. (sbox.js)

+ Implemented my own super-short Android compatibility hack into menus. It only does the basics, but you don't need more because AFAIK, all parent menus have an equivalent link in their children. And it's only 21 more bytes, eh eh. Likely in reaction to Ant's comment at Elk about how Superfish got bloated to add mobile support... ;) (script.js)