title: permissibility of 'href=javascript:(<functon_name>(<map_node_id>)' in chrome-extension mv2/mv3
body: <p>This question relates to dynamic generation of clickable image maps (eg via graphviz dot, etc.), and acceptable coding practices in an extension...</p>
  <ol>
  <li>providing a URL in an area tag of the imagemap that forces any navigation will not be appropriate.</li>
  <li>the only way for this to actually work is the inclusion of a &quot;href=javascript:(...)&quot; where the id of the area tag, and/or other parameters are provided as argument(s) to the referenced Javascript function&quot;</li>
  </ol>
  <p>Problem is, as I understand, this method of 'invocation of javascript' (the eventhandler) is proscribed in extensions.  Is this the case?  If so then where.what.how...????</p>
  <p>The dataflow is generally as follows:</p>
  <p><BR>1) extension gui forwards a request to library code embedded in the application tab, requesting that it —
  <br>
  a) generate a .dot-language representation of part of that application,
  <br>
  b) forward that .dot-language representation to a remote server (hosted by the extension's developer's domain),
  <br>c) the remote .dot graphviz server returns i) the url of the graph and ii) the url of the imagemap of that graph, to the library embedded in the application,
  <br></p>
  <p><br>2) the library embedded in the application, forwards the url's to the extension,
  <br>3) the extension retrieves and displays the generated image and applies the imagemap.</p>
  <p>Now we have a static image displayed.  This is part of what the extension already accomplishes</p>
  <p>However -- to make it even more useful and a better investigative/SDK tool, click events on the areas in the imagemap need to processed via javascript (this code IS included in the extension, it is not imported or loaded dynamically), to retrieve, organize and display associated data for the 'clicked' node in the graph.  Navigation in response to a click event in the map is out of the question.</p>
  <p>What I &gt;was&lt; planning on doing was providing the href=javascript:(...) attribute for when the imagemap is generated by the .dot server.  I don't want to have to re-invent the wheel and parse the returned imagemap into an geometrically ordered set and then match a click event's coordinates against that ordered set to figure out what id/parameter to feed the final javascript function that generates messages to retrieve the associated data.  whew !!</p>
  <p>Thank you in advance..</p>