Wedge

I think I heard about it in the last season of Fringe.

Oh, I've always heard that the latest Who was better than the crap we have in the weeks before..?
(Anything with Neve McIntosh is bound to be good anyway... She was my favorite character in Gormenghast :P)

Nothing to add. ;)

So, I fixed it in two different ways...

- a CSS-only fix, doesn't work in IE 6-8 (it'll still work -- just not that particular bug.)[1]
- a JS+CSS fix, works everywhere.[2]

CSS version adds 12 bytes to CSS file, and 0 byte to JS file.
JS version adds 1 byte to CSS file, and 6 bytes to JS file.

JS version seems like a no-brainer, but I prefer adding bytes to CSS (= doesn't stall page loading), and it's easier to save bytes in CSS than in JS, because the JS file is already optimized for size, and by a wide margin...

Any opinions...?

PS: that particular link brings back bad memories... >_<

1.	.bbc_link span:not([class]):before
2.	.bbc_link .cut:before in CSS, and <span class="cut"> in JS.

Okay, looks like I had a few errors in my log -- I just didn't see them because every time I tested, I didn't get anything. It just evades me... Not worth discussing any longer. Bug fixed, will be in my next commit, let's talk about something else...

Actually, it's not the link shortener that's changing the style, it's the .bbc_link class, which is shown on all parsed links...

Hmm, I don't know how to 'fix this'... (Does it REALLY need fixing..? :^^;:)
Taking apart the cool existing code to add some stuff to remove BBC tags from the char counter...? (Hmm, I don't even remember how I did that one...)

It iterates through the array called mkArray, all items except for the first (1 to length-1).

I'll have a look at your code.

Okay, so I had a look at your code... Didn't get it at first, ah ah.


This should work, as I tested it in the console... If it doesn't, it means your code can't execute while loading, so you'll have to load it inside an onload event, or something.
e.g., document.body.onload = function () { ... }

rev 2088 -- and here we are... The Big Fix for CSS keywords.
(11 files, 22kb) (88, 11, 22... A pattern?!)

* And another huge overhaul of Wess and the system class... Basically, we::$browser['is_*'] is now we::$browser['*'], and all of the we::$user['is_*'] variables are moved to we::$is['*'], to make them clearer to differentiate from non-boolean $user variables, basically. Finally, we::$browser OS variables are moved to we::$os, including the we::$os['mobile'] boolean, which is an alias to we::$is['mobile'] anyway. Got it..? (Class-CSS.php, Class-System.php, Display.php, Load.php, Notifications.php, Post.php, Post2.php, Profile-View.php, RemoveTopic.php, Subs-Cache.php, Subs-Template.php)

* CSS suffix overhaul. I'm no longer initializing a css_suffixes array, and instead using the system class's properties directly. This saves nearly 2KB in Load.php, really... Also added support for all kind of tests within filename suffixes, so basically index.!(opera && windows).css is now a possibility... If you're crazy enough, of course. (Load.php, Subs-Cache.php)

* CSS file caching should now be working properly for board and category IDs tested against within the CSS file itself. I spent an awful lot of time on it, and I'm pretty sure not many people are going to find this of use anyway, but I wanted to harmonize the list of keywords available between filename suffixes and @if tests. Also saves about 700 bytes of code. (Class-System.php, Subs-Cache.php)

+ Added support for the | (logical OR) delimiter in CSS tests (not in filename suffixes though, as | is not a valid filename char). You can use a comma, or |, or ||, whatever you prefer, I'm not going to judge. (Class-System.php)

! The system class could never hold board information, because loadBoard is called after it... And not only that, but I was globaling $board instead of $board_info. Anyway, fixed and moved to loadBoard instead... (Class-System.php, Load.php)

@ Note... Support for the replace keyword was rewritten, and is untested. Might go away at some point. Same for fallback folders -- it wasn't rewritten though, just left to rot. Also, the local keyword still won't work inside CSS files. And finally, plugin CSS wasn't rewritten either, and instead I chose to remove support for filename suffixes for them; I have yet to see them used by someone else than me, and I'm fine with it.

I had a very niche forum back in 2003. It was an instant success because I was the authority on that particular niche subject. But managing it was a real chore... After a few years, I voluntarily made it harder for people to post; as a result, about 90% of my users left, leaving me with way more time for my other interests, ah ah... Well, after that I turned my forum into a generalist one (noisen.com), and gathered about 5 to 10 new users in the last 6 years.  The rest are my long-time buddies who're there because they like me and they like what we talk about.

Conclusion:
- don't start a forum just because you want to compete with someone else; it has to be there to FILL a need, OR to help you get to grips with managing a website or market it; it's all about the journey, not the destination.
- don't start a forum if you're not prepared to deal with its success;
- don't start a forum if you're not using Wedge. Obviously.