Page MenuHomePhabricator

Special:Preferences: For JS-requiring features, re-use the styling that Beta Features invented and show a red warning but only to non-JS users
Open, Needs TriagePublic

Description

Special:Betafeatures distinguishes the beta features that require JavaScript in red when JavaScript is disabled. There are some editing tools (such as "edit toolbar") and other features (such as "Automatic reloading watchlist") that also required JavaScript. The fact that they require JavaScript is also mentioned through an unconditional message (shown even when JavaScript is enabled). This seems to be inconsistent with the way Beta features shows the message. Further, the message just appears as plaintext and is not distinguished as done in Special:Betafeatures.

Consistency in Special:Preferences needs to be achieved in this respect to avoid overloading users with differences like these.

Event Timeline

Kaartic triaged this task as High priority.May 11 2018, 7:27 PM
Kaartic created this task.
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptMay 11 2018, 7:27 PM
Kaartic updated the task description. (Show Details)May 11 2018, 7:29 PM
Jdforrester-WMF renamed this task from Special:Preferences, No JS: show JavaScript requirement of featues in red to Special:Preferences: For JS-requiring features, re-use the styling that Beta Features invented and show a red warning but only to non-JS users.May 11 2018, 7:55 PM
Jdforrester-WMF raised the priority of this task from High to Needs Triage.
Jdforrester-WMF added a subscriber: Jdforrester-WMF.

Yeah, this'd be nice to do. Not sure it should block deployment, but it's a good catch.

Vvjjkkii renamed this task from Special:Preferences: For JS-requiring features, re-use the styling that Beta Features invented and show a red warning but only to non-JS users to o3caaaaaaa.Jul 1 2018, 1:11 AM
Vvjjkkii triaged this task as High priority.
Vvjjkkii updated the task description. (Show Details)
Vvjjkkii removed a subscriber: Aklapper.
Kaartic renamed this task from o3caaaaaaa to Special:Preferences: For JS-requiring features, re-use the styling that Beta Features invented and show a red warning but only to non-JS users .Jul 1 2018, 12:59 PM
Kaartic raised the priority of this task from High to Needs Triage.
Kaartic updated the task description. (Show Details)
Kaartic added a subscriber: Aklapper.

From a product perspective, I wonder how this would help, given this is a rather rare choice (see No-JavaScript notes on mw.org) nowadays? Imagine I'm
a) in an environment that doesn't let me activate JS. Then it's causing at best frustration with my IT team.
b) a person concerned with several side-effects of activating JS (privacy, performance). I would be frustrated that there's another feature I'd need to give up my choice in order to use. But I would not necessarily switch JS on.
c) …?

We're aiming for progressive enhancing products at the Wikimedia Foundation in general. If a product is fundamentally dependent on JavaScript, it makes more sense to hide its preference from non-JS users than showing a warning notice given the user demographics of non-JS choice.

Some thoughts,

From a product perspective, I wonder how this would help, given this is a rather rare choice (see No-JavaScript notes on mw.org) nowadays? Imagine I'm
a) in an environment that doesn't let me activate JS. Then it's causing at best frustration with my IT team.
b) a person concerned with several side-effects of activating JS (privacy, performance). I would be frustrated that there's another feature I'd need to give up my choice in order to use. But I would not necessarily switch JS on.
c) …?

I don't have any data points but my intuition tells me these cases contribute to the minority of the users. I'm not telling to ignore them but these cases don't seem to be a show stopper for this task. The majority might be benefited as they would not see the confusing message about requirement of JS even if they have JS enabled when this task gets resolved.

We're aiming for progressive enhancing products at the Wikimedia Foundation in general. If a product is fundamentally dependent on JavaScript, it makes more sense to hide its preference from non-JS users than showing a warning notice given the user demographics of non-JS choice.

Your point seems to apply to the current state beta features too. Think about how some of them might possibly miss a feature if we hide those that require JS from non-JS users. Hiding seems to be a bad thing given that a lot of features already aren't so easily discoverable. Hiding could just make it worse.

Of course, the best solution would be to develop something that also work for non-JS users. But it's not always possible. (It might be possible if we have a lot of volunteer developers, though ;-)