Skip to content

Commit

Permalink
Set the stage for datagrid changes
Browse files Browse the repository at this point in the history
git-svn-id: http://svn.whatwg.org/webapps@116 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information
Hixie committed Sep 12, 2006
1 parent 36dafaf commit b8c5885
Show file tree
Hide file tree
Showing 2 changed files with 53 additions and 33 deletions.
44 changes: 27 additions & 17 deletions index
Expand Up @@ -24,7 +24,7 @@

<h1 id="web-applications">Web Applications 1.0</h1>

<h2 class="no-num no-toc" id="working">Working Draft &mdash; 29 August
<h2 class="no-num no-toc" id="working">Working Draft &mdash; 12 September
2006</h2>

<p>You can take part in this work. <a
Expand Down Expand Up @@ -7934,20 +7934,6 @@ https://www.google.com/base/settings
href="#scs">[SCS]</a></span> The <dfn
id="datagrid0"><code>datagrid</code></dfn> element</h4>

<p class="big-issue">It has been suggested that instead of this
flattened-row API, we should have all the "row" arguments in the API below
be arrays of integers, and instead of getParentRow(), we would have
getRowCount() get the number of children that a row had. A future version
of this specification will make this change, along with adding a way to
detect when a row/selection has been deleted, activated, etc.

<p class="big-issue">This element is defined as interactive, which means it
can't contain other interactive elements, despite the fact that we expect
it to work with other interactive elements e.g. checkboxes and input
fields. It should be called something like a Leaf Interactive Element or
something, which counts for ancestors looking in and not descendants
looking out.

<p><span title="interactive elements"><a
href="#interactive3">Interactive</a></span>, <span title="block-level
elements"><a href="#block-level1">block-level element</a></span>.
Expand Down Expand Up @@ -7991,6 +7977,30 @@ https://www.google.com/base/settings
};</pre>
</dl>

<p class="big-issue">It has been suggested that instead of this
flattened-row API, we should have all the "row" arguments in the API below
be arrays of integers (labelled as long[] in the IDL), and instead of
getParentRow(), we would have getRowCount() get the number of children
that a row had. A future version of this specification will make this
change. This will also remove the toggleRowOpenState() method. A new
method will be added to the datagrid itself to open a specific row.

<p class="big-issue">Another thing to be added is a way to detect when a
row/selection has been deleted, activated, etc, by the user (delete key,
enter key, etc).

<p class="big-issue">Also, instead of making the API have to be fully
sort-order aware, we will change it so that there is one method that is
called to get a mapping from display position to data position. Then
selection will be fully UA-driven.

<p class="big-issue">This element is defined as interactive, which means it
can't contain other interactive elements, despite the fact that we expect
it to work with other interactive elements e.g. checkboxes and input
fields. It should be called something like a Leaf Interactive Element or
something, which counts for ancestors looking in and not descendants
looking out.

<p>The <code><a href="#datagrid0">datagrid</a></code> element represents an
interactive representation of tree, list, or tabular data.

Expand Down Expand Up @@ -9058,8 +9068,8 @@ interface <dfn id="datagriddataprovider">DataGridDataProvider</dfn> {

<p>The <code title="dom-provider-getCellClasses"><a
href="#getcellclasses">getCellClasses()</a></code> method must add the
<code title="datagrid-cell-class-cyclable"><a
href="#cyclable">progress</a></code> class.</p>
<code title="datagrid-cell-class-progress"><a
href="#progress1">progress</a></code> class.</p>

<p>The <code title="dom-provider-setCellCheckedState"><a
href="#setcellcheckedstate">setCellCheckedState()</a></code>, <code
Expand Down
42 changes: 26 additions & 16 deletions source
Expand Up @@ -6460,21 +6460,6 @@ https://www.google.com/base/settings

<h4><span title="SCS">[SCS]</span> The <dfn><code>datagrid</code></dfn> element</h4>

<p class="big-issue">It has been suggested that instead of this
flattened-row API, we should have all the "row" arguments in the API
below be arrays of integers, and instead of getParentRow(), we would
have getRowCount() get the number of children that a row had. A
future version of this specification will make this change, along
with adding a way to detect when a row/selection has been deleted,
activated, etc.</p>

<p class="big-issue">This element is defined as interactive, which
means it can't contain other interactive elements, despite the fact
that we expect it to work with other interactive elements e.g.
checkboxes and input fields. It should be called something like a
Leaf Interactive Element or something, which counts for ancestors
looking in and not descendants looking out.</p>

<p><span title="interactive elements">Interactive</span>,
<span title="block-level elements">block-level element</span>.</p>

Expand Down Expand Up @@ -6505,6 +6490,31 @@ https://www.google.com/base/settings
</dd>
</dl>

<p class="big-issue">It has been suggested that instead of this
flattened-row API, we should have all the "row" arguments in the API
below be arrays of integers (labelled as long[] in the IDL), and
instead of getParentRow(), we would have getRowCount() get the
number of children that a row had. A future version of this
specification will make this change. This will also remove the
toggleRowOpenState() method. A new method will be added to the
datagrid itself to open a specific row.</p>

<p class="big-issue">Another thing to be added is a way to detect
when a row/selection has been deleted, activated, etc, by the user
(delete key, enter key, etc).</p>

<p class="big-issue">Also, instead of making the API have to be
fully sort-order aware, we will change it so that there is one
method that is called to get a mapping from display position to data
position. Then selection will be fully UA-driven.</p>

<p class="big-issue">This element is defined as interactive, which
means it can't contain other interactive elements, despite the fact
that we expect it to work with other interactive elements e.g.
checkboxes and input fields. It should be called something like a
Leaf Interactive Element or something, which counts for ancestors
looking in and not descendants looking out.</p>

<p>The <code>datagrid</code> element represents an interactive
representation of tree, list, or tabular data.</p>

Expand Down Expand Up @@ -7503,7 +7513,7 @@ interface <dfn>DataGridDataProvider</dfn> {
<p>The <code
title="dom-provider-getCellClasses">getCellClasses()</code> method
must add the <code
title="datagrid-cell-class-cyclable">progress</code> class.</p>
title="datagrid-cell-class-progress">progress</code> class.</p>

<p>The <code
title="dom-provider-setCellCheckedState">setCellCheckedState()</code>,
Expand Down

0 comments on commit b8c5885

Please sign in to comment.