Page MenuHomePhabricator

VE shoudn't replace empty values with autovalue in parameters that already exist
Open, Needs TriagePublic

Description

Now, if the field is empty, the VisualEditor replaces it with autovalue. This is completely unintuitive behavior for the user who is editing the template. The user opens the template, makes an edit in one or two fields, and when saved, it turns out that significantly more fields have changed. The user does not suspect this, because he sees already substituted values immediately upon opening.

Autovalue should only be substituted when the user explicitly adds a field. Otherwise, the editor spoils the article.

There is an example (one of many) in the screenshot when the user changes only the image, and receives a lot of changed fields.

Event Timeline

putnik created this task.Dec 10 2019, 7:55 PM
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptDec 10 2019, 7:55 PM
putnik renamed this task from No need to replace empty values with autovalue in parameters that already exist to VE shoudn't replace empty values with autovalue in parameters that already exist.Dec 10 2019, 7:55 PM
MBH added a subscriber: MBH.Dec 10 2019, 11:38 PM