<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://www.w3.org/Bugs/Public/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.4"
          urlbase="https://www.w3.org/Bugs/Public/"
          
          maintainer="sysbot+bugzilla@w3.org"
>

    <bug>
          <bug_id>21718</bug_id>
          
          <creation_ts>2013-04-16 13:55:04 +0000</creation_ts>
          <short_desc>xrefs are broken</short_desc>
          <delta_ts>2013-08-08 13:28:38 +0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>1</classification_id>
          <classification>Unclassified</classification>
          <product>CSS</product>
          <component>CSSOM View</component>
          <version>unspecified</version>
          <rep_platform>PC</rep_platform>
          <op_sys>All</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>INVALID</resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>P2</priority>
          <bug_severity>normal</bug_severity>
          <target_milestone>---</target_milestone>
          
          <blocked>21828</blocked>
          <everconfirmed>1</everconfirmed>
          <reporter name="Simon Pieters">zcorpan</reporter>
          <assigned_to name="Simon Pieters">zcorpan</assigned_to>
          <cc>glenn</cc>
          
          <qa_contact>public-css-bugzilla</qa_contact>

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>86289</commentid>
    <comment_count>0</comment_count>
    <who name="Simon Pieters">zcorpan</who>
    <bug_when>2013-04-16 13:55:04 +0000</bug_when>
    <thetext>https://dvcs.w3.org/hg/csswg/raw-file/tip/cssom-view/Overview.html#widl-Window-scrollTo-void-long-x-long-y

[[
When the scrollTo operation is invoked, the user agent must act as if the    scroll() method was invoked with the same arguments.
]]

The &quot;scroll()&quot; part is intended to be a link to the definition of scroll(). However, the build script does two things wrong that causes Anolis to not create an xref for it:

cssom-generate.js

    var IDL_ID_PREFIX = &apos;widl&apos;;

should be

    var IDL_ID_PREFIX = &apos;dom&apos;;

(to match the old style of IDs that the references use)

Second, the generated markup for a definition is:

&lt;dt class=&quot;method&quot; id=&quot;widl-Window-scroll-void-long-x-long-y&quot;&gt;
&lt;code&gt;scroll&lt;/code&gt; (....

Anolis needs a &lt;dfn&gt; element to make xrefs, so it should be something like:

&lt;dt class=&quot;method&quot;&gt;
&lt;dfn id=&quot;dom-Window-scroll&quot;&gt;&lt;code&gt;scroll&lt;/code&gt;&lt;/dfn&gt; (...

I&apos;m not sure how overloads are currently handled, maybe we should include the arguments in the ID though I personally prefer having a single definition of an overloaded method...</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>86829</commentid>
    <comment_count>1</comment_count>
    <who name="Glenn Adams">glenn</who>
    <bug_when>2013-04-26 00:19:08 +0000</bug_when>
    <thetext>(In reply to comment #0)
&gt; https://dvcs.w3.org/hg/csswg/raw-file/tip/cssom-view/Overview.html#widl-
&gt; Window-scrollTo-void-long-x-long-y
&gt; 
&gt; [[
&gt; When the scrollTo operation is invoked, the user agent must act as if the   
&gt; scroll() method was invoked with the same arguments.
&gt; ]]
&gt; 
&gt; The &quot;scroll()&quot; part is intended to be a link to the definition of scroll().
&gt; However, the build script does two things wrong that causes Anolis to not
&gt; create an xref for it:
&gt; 
&gt; cssom-generate.js
&gt; 
&gt;     var IDL_ID_PREFIX = &apos;widl&apos;;
&gt; 
&gt; should be
&gt; 
&gt;     var IDL_ID_PREFIX = &apos;dom&apos;;
&gt; 
&gt; (to match the old style of IDs that the references use)
&gt; 
&gt; Second, the generated markup for a definition is:
&gt; 
&gt; &lt;dt class=&quot;method&quot; id=&quot;widl-Window-scroll-void-long-x-long-y&quot;&gt;
&gt; &lt;code&gt;scroll&lt;/code&gt; (....
&gt; 
&gt; Anolis needs a &lt;dfn&gt; element to make xrefs, so it should be something like:
&gt; 
&gt; &lt;dt class=&quot;method&quot;&gt;
&gt; &lt;dfn id=&quot;dom-Window-scroll&quot;&gt;&lt;code&gt;scroll&lt;/code&gt;&lt;/dfn&gt; (...
&gt; 
&gt; I&apos;m not sure how overloads are currently handled, maybe we should include
&gt; the arguments in the ID though I personally prefer having a single
&gt; definition of an overloaded method...

Made some progress on this, but some further work is required.

(1) should use &apos;widl-&apos; not &apos;dom-&apos; prefixes in title, refs, etc., when referring to cssom related idl defined terms; &apos;dom-&apos; is reserved for DOM-4 related interfaces;

(2) pre-processor now wraps member term definitions with anolis compatible dfn;</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>86840</commentid>
    <comment_count>2</comment_count>
    <who name="Simon Pieters">zcorpan</who>
    <bug_when>2013-04-26 09:29:50 +0000</bug_when>
    <thetext>(In reply to comment #1)

&gt; Made some progress on this, but some further work is required.

Thanks!

&gt; (1) should use &apos;widl-&apos; not &apos;dom-&apos; prefixes in title, refs, etc., when
&gt; referring to cssom related idl defined terms; &apos;dom-&apos; is reserved for DOM-4
&gt; related interfaces;

No, dom- is used in various specs (e.g. HTML), not just the DOM spec. I&apos;d prefer to use the dom- naming convention.

&gt; (2) pre-processor now wraps member term definitions with anolis compatible
&gt; dfn;

Great.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>86868</commentid>
    <comment_count>3</comment_count>
    <who name="Glenn Adams">glenn</who>
    <bug_when>2013-04-26 13:52:55 +0000</bug_when>
    <thetext>(In reply to comment #2)
&gt; (In reply to comment #1)
&gt; &gt; (1) should use &apos;widl-&apos; not &apos;dom-&apos; prefixes in title, refs, etc., when
&gt; &gt; referring to cssom related idl defined terms; &apos;dom-&apos; is reserved for DOM-4
&gt; &gt; related interfaces;
&gt; 
&gt; No, dom- is used in various specs (e.g. HTML), not just the DOM spec. I&apos;d
&gt; prefer to use the dom- naming convention.

I disagree. I didn&apos;t invent the widl- prefix either. It is used by all documents created using respec.js, such as those in the WebApps WG and other WGs. It provides a more useful term that is neutral of the defining spec. If we were to change it, then cssom- would be more appropriate that dom-.

We no longer use the term DOM to describe the CSSOM et al functionality, so it isn&apos;t necessary or even appropriate to do so. As for the HTML spec, it is clearly defining the HTML DOM, so it isn&apos;t inappropriate to use the dom- prefix in that context.

Finally, nothing about anolis or pub tools relies on using one prefix versus another.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>87714</commentid>
    <comment_count>4</comment_count>
    <who name="Simon Pieters">zcorpan</who>
    <bug_when>2013-05-15 11:38:17 +0000</bug_when>
    <thetext>BTW I think you need to set the title attribute instead of the id attribute to make xrefs work as intended. (Anolis will generate the id attribute.)</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>