@tomhughes commented on this pull request.
> +
+ $(document).on("click", "a.edit_object_tags", async function (e) {
+ e.preventDefault();
+ e.stopPropagation();
+
+ e.target.setAttribute("disabled", true);
+
+ const [, type, id] =
location.pathname.match(/\/(node|way|relation)\/([0-9]+)/);
+ const objectInfo = await downloadObjectInfo(type, id);
+ const currentTags = extractTagsFromObjectInfo(objectInfo);
+
+ const $browseSection = $("#sidebar_content h2 + div").first();
+
+ const $errorBox = $("<p>");
+
+ const $editorTextarea = $("<textarea>")
> The big question: should this be a simple text area or something more
> structured? If it’s a simple text area that depends on a format of some sort,
> we need to provide hard-to-miss access to documentation about the format. It
> isn’t quite [Level0L](https://wiki.openstreetmap.org/wiki/Level0L), it’s the
> [multiline key-value
> syntax](https://wiki.openstreetmap.org/wiki/Tags#key=value_syntax) that iD
> exposes in its text view.
Even if we do offer a simple text area (and I suspect we shouldn't) then it
definitely shouldn't be the default.
--
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/pull/6758#discussion_r2744038737
You are receiving this because you are subscribed to this thread.
Message ID:
<openstreetmap/openstreetmap-website/pull/6758/review/[email protected]>_______________________________________________
rails-dev mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/rails-dev
