Closed
Bug 785993
Opened 12 years ago
Closed 4 years ago
Revision history: Add amount of changed words to revision comment
Categories
(developer.mozilla.org Graveyard :: Editing, enhancement)
developer.mozilla.org Graveyard
Editing
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: fs, Unassigned)
References
Details
(Whiteboard: [type:feature])
In Deki revision comments we had both, the comment the editor entered and the amount of changed words. I liked that and I think it's a useful information on the history page. So instead of: <my revision comment> let's have: <my revision comment>; xx words added, yy words removed See for example: https://developer.mozilla.org/en-US/docs/MathML/Element/math$history
Reporter | ||
Comment 1•12 years ago
|
||
And if an editors enters no revision comment at akk, there is currently no comment at all in the revision history. I would expect to have at least the amount of changed words then. "xx words added, yy words removed" (If no words were changed, Deki added "no changes" as a comment, but I hope Kuma will not save a new revision then anyway)
Updated•12 years ago
|
Priority: -- → P3
Assignee | ||
Updated•12 years ago
|
Version: Kuma → unspecified
Assignee | ||
Updated•12 years ago
|
Component: Docs Platform → Editing
Updated•12 years ago
|
Whiteboard: p=
Updated•12 years ago
|
Whiteboard: p= → u=user
Updated•12 years ago
|
Whiteboard: u=user → u=user c=Editing
Updated•12 years ago
|
Priority: P3 → P2
Comment 2•11 years ago
|
||
Contributor system64 has been working on this. This is pretty difficult to implement, for MDN or anywhere else. Florian, David, Sheppy: What do you think about listing "(x% changed)" somewhere in the revision history instead? It would be easier to implement, but would it still provide you with the information you need?
Flags: needinfo?(dwalsh)
Whiteboard: u=user c=Editing → [type:feature]
Comment 3•11 years ago
|
||
(In reply to John Karahalis [:openjck] (PTO until April 29, 2013) from comment #2) > Florian, David, Sheppy: What do you think about listing "(x% changed)" > somewhere in the revision history instead? It would be easier to implement, > but would it still provide you with the information you need? It would be enormously more useful if it were something you would see while glancing through the list of changes in the revision dashboard (that's why we suggested adding it to the comment). The reason is simple: if you're flipping through the list in a hurry and see some enormous word change count on a long-standing article, that's a huge red-flag that someone has probably screwed something up.
Comment 4•11 years ago
|
||
We could add this information to the revision dashboard with either style. Would %-style be good enough in helping you find enormous changes?
Comment 5•11 years ago
|
||
(In reply to John Karahalis [:openjck] (PTO until April 29, 2013) from comment #4) > We could add this information to the revision dashboard with either style. > Would %-style be good enough in helping you find enormous changes? Yeah, a percentage would be fine for that (although I'd still like to be able to see an actual number of words changed somewhere, but that could go in the history).
Comment 6•11 years ago
|
||
Sounds fine to me, but no idea how you could calculate that percentage.
Flags: needinfo?(dwalsh)
Comment 7•11 years ago
|
||
(In reply to David Walsh :davidwalsh from comment #6) > Sounds fine to me, but no idea how you could calculate that percentage. Percentage of lines changed? Doesn't need to be perfect.
Comment 8•11 years ago
|
||
"Lines" doesn't work well because one line could be an entire paragraph (or an entire long, long table). It wouldn't be a useful gauge of the actual degree of change.
Updated•10 years ago
|
Severity: normal → enhancement
Priority: P2 → --
Comment 9•4 years ago
|
||
MDN Web Docs' bug reporting has now moved to GitHub. From now on, please file content bugs at https://github.com/mdn/sprints/issues/ and platform bugs at https://github.com/mdn/kuma/issues/.
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WONTFIX
Updated•4 years ago
|
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•