Promote the mobile error reporting interface (mobile.errorReport) to beta for testing.
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| Remove errorReport from MobileFrontend | mediawiki/extensions/MobileFrontend | master | +0 -251 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | • bmansurov | T100297 [EPIC] Turn off alpha | |||
| Resolved | • Jhernandez | T100704 Remove 'Report an error' from MobileFrontend | |||
| Resolved | • Nirzar | T91473 OOjs UI and MediaWiki UI buttons are different sizes | |||
| Resolved | Volker_E | T93290 ButtonElements with no label, icon and indicator should still have consistent height | |||
| Resolved | • Nirzar | T94750 In MediaWiki theme, button height should be controlled only by 'padding' and label 'line-height' | |||
| Duplicate | None | T97048 Find another/a better place for secondary actions |
I'm still curious how this is different from talk? Could we make it part of the talk feature?
I've always been confused about what that button is for - reporting an error for the current page or the site..? Also is it software errors or article errors?
I'm also on the fence about this feature. What are the goals of this feature?
Also is it software errors or article errors?
… and is this reflected in the copy?
What's the state of this? @JKatzWMF ?
If we do push this to beta we should also increase the qunit code coverage from 23.53%
@Jdlrobson: I'm not sure. I think we're going to have to have a meeting to discuss the alpha features still in Should Have.
@kaldari: Could you answer @Jdlrobson's questions/provide more detail in general?
I'm still curious how this is different from talk? Could we make it part of the talk feature?
At the time it was developed, we didn't have Talk in stable and this was intended to be a sort of Talk-light for reporting errors in articles.
I've always been confused about what that button is for - reporting an error for the current page or the site..? Also is it software errors or article errors?
When you click the button it gives you a full explanation.
Now that we have talk... is this needed? Any good ideas that we could take and fold into the talk feature e.g. provide more guidance - for example a drop down saying what the error I've seen is about? Given this is probably an editing feature I'm not sure if this is now in our interest to pursue..
4:22 PM <kaldari> jdlrobson: fine with me, you can also kill it if you like. I didn't follow discussion about it's fate, but it was originally written because we didn't have talk pages in mobile stable, so I though maybe it could be an alternative for a particular use case.
4:23 PM <kaldari> i.e. so that people on mobile could at least flag serious problems with articles.
I think we should kill this. I'm not sure what purpose it fills with talk.
We can feature branch it and bring it back if necessary.
Change 231462 had a related patch set uploaded (by Jdlrobson):
Remove errorReport from MobileFrontend
@kaldari would you mind documenting this - or pointing us to a url describing the idea and rationale?
Added it here https://www.mediawiki.org/wiki/Reading/Web/2015_Q1_Feature_stabilization.
If somebody wants to document the feature it would be great. ^ @kaldari?