HTTPSE up to 5.0development.0 + FF (31): Broken re-ordering in the "Enable / Disable Rules" window

When you re-order the rules by name and then close the HTTPS Everywhere window, they all revert to their previous order.

added component::https everywhere/eff-https everywhere options ordering owner::zyan priority::high resolution::invalid rules severity::normal status::closed type::defect window labels

Trac:
Cc: N/A to jsha@newview.org

What's the intended behavior? Should rules always be sorted by name?

Replying to jsha:

What's the intended behavior? Should rules always be sorted by name?

They should appear the way they were left, as in 3.4.5. This was part of the [https://trac.torproject.org/projects/tor/ticket/11529#comment:2] problem, not fixed along with the main issue. Now every time I open the options window the rules are sorted the way they were deployed during the last session before I upgraded to 3.5.1 (Tor first, then rules for visited sites, then all the rest), and no kind of re-ordering them is persistent. (Ordering by the "enabled" column is quite impossible, the button doesn't work).

Trac:
Summary: HTTPS-E 3.5.1 + FF 29: Broken re-ordering in the "Enable / Disable Rules" window to HTTPSE up to 5.0development.0 + FF (31): Broken re-ordering in the "Enable / Disable Rules" window
Milestone: HTTPS-E 3.5 to N/A

Perhaps it should be prioritized higher, since it turns a privacy-oriented add-on into a bit of a tracker, and the solution is already there, somewhere in the code of 3.4.5 or older.

Trac:
Keywords: rules order deleted, rules ordering options window added
Priority: normal to major

Pull request for this at https://github.com/EFForg/https-everywhere/pull/813

Half-repaired as of HTTPSE 5.0.3, the rules are now always ordered alphabetically, only the bar keeping the last state (i.e. there can be a discord between the sorting bar & the list below). Still no possibility of sorting by "Enabled".

I've been meaning to revamp this interface dramatically so it is not required to load all rulesets before displaying, which is very slow, and not very meaningful with 15k+ rules. Probably this will mean offering a search box that only starts displaying once two or more characters are loaded, and searches across filenames rather than name attributes.

Can you tell me more about your use case for sorting by enabled so I can figure out how that would fit into a revamped UI?

Obsolete as the window does not exist any longer in the current version of HTTPS-Everywhere.

Trac:
Severity: N/A to Normal
Status: new to closed
Resolution: N/A to invalid
Sponsor: N/A to N/A

closed

moved to tpo/applications/https-everywhere-eff#11655 (closed)