@deevroman 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>")
Maybe the motivation was really like that, but in my practice there are still a
few advantages:
1. A wider field. There are no additional buttons, and the keys column does not
take up a fixed width
2. Works arrow navigation on the keyboard
> future enhancement for syntax highlighting
well, so far there is no CodeMirror even in the iD :)
--
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/pull/6758#discussion_r2743934490
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
