Since there are anchors, is there any cost to replacing context=1 with context=3 ?
Alternatively, context for the parent button (or even the permalink button) could be controlled from the preferences page, at the cost of UI proliferation. This might make more sense for people who want context on the recent comments page, which is a feature that would have cost to people who don’t want it. (hmm...I guess greasemonkey could make parent=context=3)
Incidentally, the combination of deleted comments and context is buggy. If you go here where the parent is deleted and visible, there’s no obvious way to proceed up (permalink, then parent is a non-obvious escape). If there are two deleted comments in a row, I think it’s impossible to navigate up, short of editing the URL to context=9.
I’d like more context.
Since there are anchors, is there any cost to replacing context=1 with context=3 ?
Alternatively, context for the parent button (or even the permalink button) could be controlled from the preferences page, at the cost of UI proliferation. This might make more sense for people who want context on the recent comments page, which is a feature that would have cost to people who don’t want it. (hmm...I guess greasemonkey could make parent=context=3)
Incidentally, the combination of deleted comments and context is buggy. If you go here where the parent is deleted and visible, there’s no obvious way to proceed up (permalink, then parent is a non-obvious escape). If there are two deleted comments in a row, I think it’s impossible to navigate up, short of editing the URL to context=9.