Databases
StackOverflow2013
Postsdbo
POChrome does not scroll the focused editable row to the viewport
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POChrome does not scroll the focused editable row to the viewport
    text
    copied!<p>This issue is only happening in Chrome. (jqgrid v 4.4.1)</p> <p>I have a grid with one editable cell in each row. When updating those editable fields I move the focus to the next enable field in the grid so that row will get selected. </p> <p>The issue is, if the next focused field is not in the current viewport the browser(not chrome) itself scrolls that record to the viewport and user can see it. But this is not happening in Chrome (not scrolling the focused record to the viewport).</p> <p>I create these editable cells using jqgrid custom formatter as I need different type of input fields to be created.</p> <p>When the type is radio or a combo (select) chrome works fine, scrolls the focused element to the screen, but when the type is 'text' this is not happening in chrome. And I could not find any logical reason for this.</p> <p>These are the fields created, </p> <p>Radio:</p> <pre><code>&lt;td role="gridcell" style="" aria-describedby="myGrid_editCol"&gt; &lt;span class="editable"&gt; &lt;div class="customelement" id="36_editCol" name="editCol"&gt; &lt;input id="36_editCol_id1" name="36_editCol_nm" type="radio" value="0"&gt; No &lt;input id="36_editCol_id2" name="36_editCol_nm" type="radio" value="1" checked="checked"&gt; Yes &lt;input id="36_editCol_id3" name="36_editCol_nm" type="radio" value="?"&gt; Unknown &lt;/div&gt; &lt;/span&gt; </code></pre> <p></p> <p>Text:</p> <pre><code>&lt;td role="gridcell" style="" aria-describedby="myGrid_editCol"&gt; &lt;span class="editable"&gt; &lt;div class="customelement" id="75_editCol" name="editCol"&gt; &lt;input type="text" id="75_editCol_id" maxlength="10" value="sd"&gt; &lt;/div&gt; &lt;/span&gt; </code></pre> <p></p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload