[
http://jira.dspace.org/jira/browse/DS-549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Donohue reassigned DS-549:
------------------------------
Assignee: Peter Dietz
Assigning to PeterDietz to test and review the patch.
We discussed this issue in today's DSpace Devel Meeting:
[20:17] <tdonohue> Allow anchor tags/Xref objects in the XMLUI to have an 'id'
attribute. : http://jira.dspace.org/jira/browse/DS-549
[20:18] <richardrodgers> Any sense of how disruptive this would be?
[20:18] <tdonohue> seems simple enough -- it seems like the whole goal is just
to allow for the final XHTML <a> elements to have @id
[20:19] <jatrimble> As long as it is optional, it would have backword
compatability issue in web design.
[20:20] <tdonohue> good point, jatrimble -- I think it would be -- as the
themes/CSS don't look for an @id attribute right now (as it isn't possible)
[20:20] <tdonohue> Any volunteers to look into this a bit more?
[20:21] <PeterDietz> I can test the patch
[20:21] <jatrimble> exactly........ with css, backwords compatability is
essential until something in css is depricated.
[20:21] <tdonohue> ok, thanks PeterDietz
[20:21] <tdonohue> Assign DS-549 to PeterDietz for testing and analysis
> Allow anchor tags/Xref objects in the XMLUI to have an 'id' attribute.
> ----------------------------------------------------------------------
>
> Key: DS-549
> URL: http://jira.dspace.org/jira/browse/DS-549
> Project: DSpace 1.x
> Issue Type: Improvement
> Components: XMLUI
> Environment: Any
> Reporter: Jason Gum
> Assignee: Peter Dietz
> Priority: Minor
> Attachments: addIdToXref.patch
>
>
> Hi everyone,
> Currently the XMLUI framework does not allow one to add an id to an anchor
> tag. This prevents code such as <a id="myUniqueId" class=" " href="#"> from
> being generated even though it is still valid XHTML code. I have attached a
> patch with changes that would allow such an id to be set.
> This feature was requested to allow linking within the same page. An example
> of the code in use can be found at https://ritdml.rit.edu/FAQ.
> Regarding the specific code changes: The standard order for elements that
> have names(ids) seem to be context first, name second, and then the remaining
> parameters, usually ending with rend, but I made this constructor take name
> as the last parameter to maximize backwards compatibility. I will allow
> someone else to decide what is more important.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.dspace.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
This SF.net email is sponsored by
Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
