Root / Site Discussion / [.]
BBCode that is normally not allowed in certain fields (such as thread posts), they'll appear, but won't when actually posted.It's too much work to fix this right now (like a LOT of work), so it's just gonna have to stay. It's the user's fault if they're using bbcode that doesn't show up in the toolbox lol. The bbcode "query" page only accepts text; it does not accept a bbcode "parse type". I'd have to tell each toolbox to store the type inside the preview button (or something), then extract it and send it off when you click preview. I'd also have to modify the query page to accept and understand a request for different bbcode types Edit: And someone's already posted about HTML working in the preview. Again, it's too much work to fix right now; there are other things that are more important, I think.This text is big when previewing, but the disabled BBCode will show the tags normally.
Also HTML will also work on BBCode previews. (will show the tags when viewing normally) <a href="/cheese">Nothing</a>
I'm watching the SB Bug Reports thread, so I get a notif every time a new thread is made their. Great feature, thanks for adding it (even better than the new threads alert thing on the category page, which I personally hate and turned off.) But I found a bug with it. If you open the notification you got about the thread being created, it doesn't clear. You have to actually visit the forum category page to properly clear the notification.Not a bug, and it's actually been reported twice before I believe. It's because it would require special code just to search through your notifications and remove that one, since notifications are NOT set up to be individually cleared. Remember, new thread notifications are grouped under "thread category", not individual threads. The system works with events and a sliding window, and there's no way to remove a particular notification from a group unless it just so happens to pass below the sliding window. Basically, I'd have to change the entire system just to get this to work, and it's really not worth it in my opinion. It's only one extra click to clear out the new thread notifications, but it's a landslide of code changes to make it automatic.
It appears as a notification set for that specific thread though, so it's confusing. Maybe you should group them under a "New Threads" specifier in the notifications screen? I dunno.I'm watching the SB Bug Reports thread, so I get a notif every time a new thread is made their. Great feature, thanks for adding it (even better than the new threads alert thing on the category page, which I personally hate and turned off.) But I found a bug with it. If you open the notification you got about the thread being created, it doesn't clear. You have to actually visit the forum category page to properly clear the notification.Not a bug, and it's actually been reported twice before I believe. It's because it would require special code just to search through your notifications and remove that one, since notifications are NOT set up to be individually cleared. Remember, new thread notifications are grouped under "thread category", not individual threads. The system works with events and a sliding window, and there's no way to remove a particular notification from a group unless it just so happens to pass below the sliding window. Basically, I'd have to change the entire system just to get this to work, and it's really not worth it in my opinion. It's only one extra click to clear out the new thread notifications, but it's a landslide of code changes to make it automatic.
I did that and then people wanted them split off into the thread they're for. IDK, I'll think of something, but I can't make everyone happy.It appears as a notification set for that specific thread though, so it's confusing. Maybe you should group them under a "New Threads" specifier in the notifications screen? I dunno.I'm watching the SB Bug Reports thread, so I get a notif every time a new thread is made their. Great feature, thanks for adding it (even better than the new threads alert thing on the category page, which I personally hate and turned off.) But I found a bug with it. If you open the notification you got about the thread being created, it doesn't clear. You have to actually visit the forum category page to properly clear the notification.Not a bug, and it's actually been reported twice before I believe. It's because it would require special code just to search through your notifications and remove that one, since notifications are NOT set up to be individually cleared. Remember, new thread notifications are grouped under "thread category", not individual threads. The system works with events and a sliding window, and there's no way to remove a particular notification from a group unless it just so happens to pass below the sliding window. Basically, I'd have to change the entire system just to get this to work, and it's really not worth it in my opinion. It's only one extra click to clear out the new thread notifications, but it's a landslide of code changes to make it automatic.
It doesn't work for me. I also can't vote on pages. (Using Safari on iOS)We've had endless trouble trying to support safari. We just don't now; I'm sorry. Please download Chrome or Firefox for iOS. The system to show the votes already has hacks to support webkit's silly rules. I don't want to add even more hacks just because safari is lame. It's a simple :focus rule; I don't know why browsers have to make it so complicated. Also, even I weren't just complaining, I don't have a single apple product to test any of this stuff on. Sorry! Edit: So apparently there's a lot of stuff broken on Safari:
Well, it works well enough; (I wouldn't consider 3 things to be "a lot", anyway)It doesn't work for me. I also can't vote on pages. (Using Safari on iOS)We've had endless trouble trying to support safari. We just don't now; I'm sorry. Please download Chrome or Firefox for iOS. The system to show the votes already has hacks to support webkit's silly rules. I don't want to add even more hacks just because safari is lame. It's a simple :focus rule; I don't know why browsers have to make it so complicated. Also, even I weren't just complaining, I don't have a single apple product to test any of this stuff on. Sorry! Edit: So apparently there's a lot of stuff broken on Safari:I'm sorry, we just don't support Safari.
- Can't reply to comments
- Can't vote on pages
- Can't see votes on polls
