Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rename #map to #imageMap? #826

Open
GoogleCodeExporter opened this issue Mar 25, 2015 · 4 comments
Open

Rename #map to #imageMap? #826

GoogleCodeExporter opened this issue Mar 25, 2015 · 4 comments

Comments

@GoogleCodeExporter
Copy link

Currently the map tag is used for image maps. Maps can also have areas. The map 
tag renders an anchor, which is wrong in the case of rendering areas.

Therefor: Should we rename #map to #imageMap and then reintroduce #map to be 
used for areas?

See http://www.w3.org/TR/html4/struct/objects.html#include-maps and 
http://dev.w3.org/html5/spec-preview/the-map-element.html#the-map-element.

Original issue reported on code.google.com by adriaan....@gmail.com on 24 Aug 2014 at 10:22

@GoogleCodeExporter
Copy link
Author

I do not get the necessity of having an imageMap-Tag. Reading the spec of the 
<a> Anchor-tag there is no hint to a specific callback behavior. Does anyone 
know, why WAImageMapTag>>callback: was implemented?

#map should be replaced with a MapTag (<map>) and area-tag needs to be 
implemented - possibly as anchor, depends on the corresponding attributes. I 
could take care of this issue, and check the attributes and where to locate map 
and area tag, ok?

Original comment by max.bar...@googlemail.com on 28 Aug 2014 at 8:51

  • Added labels: ****
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author

I worked on the area tag. The code is here: 
http://smalltalkhub.com/#!/~a3aan/SeasideSprintArea.

Original comment by adriaan....@gmail.com on 28 Aug 2014 at 10:20

  • Added labels: ****
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author

There are two kinds of image maps:
- "server side": the client just sends to coordinates to the server and the 
server has to figure out what has been clicked (eg. which country on a map)
- "client side": the client figures out which element has been clicked (eg. 
which country on a map) and sends that to the server

WAImageMapTag implements the "server side" variant. A MapTag (<map>) would 
implement the "client side" variant.

The documentation for server side is here: 
http://www.w3.org/TR/html4/struct/objects.html#didx-server-side_image_map
>Server-side. When a user activates a region of a server-side image map with a 
mouse, the pixel coordinates of the click are sent to the server-side agent 
specified by the href attribute of the A element. The server-side agent 
interprets the coordinates and performs some action.

We obviously need both. In theory WAImageMapTag could be replaced by an 
#imageMapCallback: or similar on WAAnchorTag.

The hard thing about doing a MapTag (<map>) is coming up with a good API. For 
example to create a circle what should be API look like

html map
    beCircle;
    coordinates: ...


html map
    beCircle: aWACircle


html map
    beCircleAt: aPoint withRadius: aNumber



html map
    circleAt: aPoint withRadius: aNumber


Should be support in image geometry objects? Should we have our own? What 
should the argument of the callback be, a geometry object, a business object?

Original comment by philippe...@gmail.com on 28 Aug 2014 at 11:28

  • Added labels: ****
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author

Original comment by jo...@yesplan.be on 19 Oct 2014 at 6:04

  • Added labels: Version-Seaside3.2
  • Removed labels: ****

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants