Change Details

There are a few `mapframe`/`maplink` configurations that Visual Editor doesn't support yet. [] maplink and mapframe auto-positioning -- absence of longitude / latitude / zoom parameters [] editing non-static map features -- when GeoJSON contains `ExternalData` blocks [] Wikivoyage tags using `group` and `show` parameters Currently we are never blocking the user from entering in the Visual Editor mode, although the editor experience can be awkward and frustrating in these situations, and can lead to unexpected results, broken map, and data loss. When we know the editor is not working properly, we should at the very least warn users that the editor is not a stable, full-featured product yet. Another option is to fix this lack of features by implementing them, but this is likely to take more time, if done right.

There are a few `mapframe`/`maplink` configurations that Visual Editor doesn't support yet. [] **Maplink and mapframe auto-positioning** -- absence of longitude / latitude / zoom parameters | Raw editor | VE inline editing | VE map dialog | Expected result | | --- | --- | --- | --- | {F5630724} | {F5630726} | {F5630729} | {F5630731} [] **Editing non-static map features** -- when GeoJSON contains `ExternalData` blocks | Raw editor | VE inline editing | VE map dialog | Expected result | | --- | --- | --- | --- | {F5630703} | {F5630706} | {F5630708} | {F5630715} [] Wikivoyage tags using `group` and `show` parameters Currently we are never blocking the user from entering in the Visual Editor mode, although the editor experience can be awkward and frustrating in these situations, and can lead to unexpected results, broken map, and data loss. When we know the editor is not working properly, we should at the very least warn users that the editor is not a stable, full-featured product yet. Another option is to fix this lack of features by implementing them, but this is likely to take more time, if done right.

There are a few `mapframe`/`maplink` configurations that Visual Editor doesn't support yet. [] m**Maplink and mapframe auto-positioning** -- absence of longitude / latitude / zoom parameters | Raw editor | VE inline editing | VE map dialog | Expected result | | --- | --- | --- | --- | {F5630724} | {F5630726} | {F5630729} | {F5630731} [] e**Editing non-static map features** -- when GeoJSON contains `ExternalData` blocks | Raw editor | VE inline editing | VE map dialog | Expected result | | --- | --- | --- | --- | {F5630703} | {F5630706} | {F5630708} | {F5630715} [] Wikivoyage tags using `group` and `show` parameters Currently we are never blocking the user from entering in the Visual Editor mode, although the editor experience can be awkward and frustrating in these situations, and can lead to unexpected results, broken map, and data loss. When we know the editor is not working properly, we should at the very least warn users that the editor is not a stable, full-featured product yet. Another option is to fix this lack of features by implementing them, but this is likely to take more time, if done right.