forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From iss...@cocoondev.org
Subject [JIRA] Commented: (FOR-276) fork / jump functionality in document-v20
Date Sun, 05 Sep 2004 01:47:33 GMT
The following comment has been added to this issue:

     Author: David Crossley
    Created: Sat, 4 Sep 2004 8:47 PM
       Body:
See discussion in the thread:
Re: fork in doc-v20?
http://marc.theaimsgroup.com/?l=forrest-dev&m=109432782804135
---------------------------------------------------------------------
View this comment:
  http://issues.cocoondev.org//browse/FOR-276?page=comments#action_11474

---------------------------------------------------------------------
View the issue:
  http://issues.cocoondev.org//browse/FOR-276

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: FOR-276
    Summary: fork / jump functionality in document-v20
       Type: Improvement

     Status: Unassigned
   Priority: Minor

    Project: Forrest
 Components: 
             Forrest skins
   Versions:
             HEAD

   Assignee: 
   Reporter: Rick Tessner

    Created: Sat, 4 Sep 2004 4:45 PM
    Updated: Sat, 4 Sep 2004 8:47 PM

Description:
Document V1.x had the <fork> and <jump> elements available for defining hyperlinks.
 Document V2.0 removed those elements in favour of a single <a> element.

The attached patch will restore that functionality in Document V2.0 via the use of the class
attribute on <a>.

<fork href="xyz.html"> in document v1.3 would become <a href="xyz.html" class="fork">
in document v2.0.

In the same manner, <jump href="xyz.html"> becomes <a href="xyz.html" class="jump">



---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.cocoondev.org//secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


Mime
View raw message