That mostly depends on the browser. After that, it’s markup-reliant (if the SR and the browser are fairly up to date). For example, the notification area in the header uses the navigation role for the list
incorrectly I might add, ul’s cannot have the role of navigation because it already has another native role (listitem) and is only allowed certain other roles… navigation is NOT one of them
And uses aria-hidden to hide some weird icon things and has hidden text like “notifications of @name mentions, replies to your posts and topics, private messages, etc” for the first item, and so on, inside an otherwise normal anchor.
So that kind of stuff works (tho that navigation role may trip someone up, and often it’s different for SR-browser pairs… so something might work okay in Firefox but not IE, or other way around).
I’m unclear when things I see are part of basic Discourse and which is Sitepoint… like the role on the ul in the header. If that’s not SitePoint’s, I have no problem bringing mah b*tchin over to Jeff’s group. : P
95% is in the core of Discourse. The only big changes that were made by Sitepoint is the theme (the colors), some minor alterations to your Profile page, and customization of the Categories page. The rest is fairly stock. Most of the alterations were made by overriding stylesheets and not actually altering the markup.
Hi 187skillz - glad you came over to join us here. And congratulations to you, too - you’re the first member I’ve spotted with a number, not a letter, for an avatar.
Were there any optimizations done by the SP team recently? I noticed an almost double increase in the rendering speed of that php topic in Firefox and SeaMonkey, and Chrome became as fast as the other browsers. Possibly other pages became faster, too, but I’m mostly noticing this on larger threads.
On my mobile phone the improvement is also apparent - still the speeds are far from convenient but in Opera after about 15 seconds the topic is loaded fine and scrolling is fast and smooth. Generally, the site works okay if the user is patient enough. However, mobile Chrome still has serious problems - scrolling is slow and jerky, text takes time to appear or change from blurry to readable and most of the code blocks show as pixelated garbage - better than before but still broken.
BTW, how do I quote a nested reply in this new forum? In the quote above it is not clear where my quote finishes and where cpradio’s starts. I quoted this by selecting the block of text and hitting reply.
Not that i’m aware of. The version we are running was made 11 days ago. We may have upgraded to it in the last 5 days, but I can’t be sure when we actually choose to upgrade.
There were Performance improvements to the version we are on, so it is “likely” that would have helped. I know the Discourse team has been playing around with Mobile performance ever since we reported this issue (using the thread you found).
Edit: However, you are right, it has greatly improved… Oh! You know what, I do know what has changed. We added 8 more worker processes. That likely is the speed/performance increase.
I won’t say it is the “best” Discourse can do, as I know they can obviously do better, but the nested quote just isn’t a high priority for them at this moment (they are focused on other tasks).
Okay everyone! I officially moved the Opera related discussions to their own topic as they are being too noisy in what is a “Welcome to the New SitePoint Forums” discussion. Please use the following thread to discuss your love for Opera or your desire for Opera lovers to “just get over it and upgrade”
@Stomme_poes@Lemon_Juice
I’ve created a new topic for discussion Accessibility (as I don’t want it to take the same course Opera discussions took )
Please, write up anything you think will help. I have no qualms about trying to improve things, but I can only improve what I know about and I’ll be the first to admit, I know very little about Accessibility.
You can ask @TechnoBear, I took care of most of the keyboard issues as of late so that effectively works far better than it did a month ago. I’m sure I can do the same with Accessibility.
[quote=“cpradio, post:241, topic:741”]
Edit: However, you are right, it has greatly improved… Oh! You know what, I do know what has changed. We added 8 more worker processes. That likely is the speed/performance increase.[/quote]
So it must be this! Good to know things are improving.
I think there is still much room for improvement because even waiting 15 seconds (on a mobile phone) for a bunch of text to appear still seems a lot. And even if a thread is long it loads in small chunks so this shouldn’t cause such big delays. I’m sure there is room for optimization. But it’s good to know Discourse authors are willing to cooperate and improve things.
Okay, good to know. Maybe some day in the future we will be honoured when this feature is added
Yes, it will be. We have to keep in mind that Discourse is still in its infancy (to a degree). As they mature and gain a larger following, some of these “UI” issues will likely get addressed.
The Discourse team has done very well at identifying issues and helping get them resolved as our site begins to attract larger number of users and a larger dataset of topics/posts. One thing that is also in the works is changing how many of the templates are rendered and how the scripts get included. This may also give Android devices better performance.
or your desire for Opera lovers to “just get over it and upgrade” 
)