-
28 Jun 2012 6:59 AM #1
Input field not aligned with cell when editing a cell in a grid
Input field not aligned with cell when editing a cell in a grid
REQUIRED INFORMATION
Ext version tested:- Ext 4.1.0
- FF 13.0.1 (Windows) (Firebug: 1.9.2)
- IE8
- Chrome 20 (Windows) (The bug doesn't happen on Chrome)
- <!DOCTYPE html>
- After scrolling in a page, when double clicking on an editable grid, the input field appears below where is should be and a second scrollbar appears on the page. Code generated with Sencha Architect 2. Tried it with ExtJS 4.0.7 and it works correctly on that version.
- Have a page with an editable grid that is long enough to allow you to scroll
- Scroll on the page (when you click on the grid to edit it you can't be at the top of the page)
- Double click on an editable cell
- The input field should have been aligned with the original cell
- The input field doesn't align with the original cell
- A second scrollbar appears
Code:Ext.define('MyApp.view.MyViewport', { extend: 'Ext.container.Viewport', autoScroll: true, initComponent: function() { var me = this; Ext.applyIf(me, { items: [ { xtype: 'container', height: 1080, renderTpl: [ '<p>Container</p>' ], tpl: [ '' ] }, { xtype: 'gridpanel', title: 'My Grid Panel', store: 'MyArrayStore', columns: [ { xtype: 'gridcolumn', dataIndex: 'string', editor: 'textfield', text: 'String' } ], plugins: [ Ext.create('Ext.grid.plugin.CellEditing', { ptype: 'cellediting' }) ] } ] }); me.callParent(arguments); } });
HELPFUL INFORMATION
Screenshot or Video:- Complete Sencha Architect 2 project attached
- Screenshot attached
- none
- not provided
- only default ext-all.css
- WinXP Pro
ExtJsIssue.png
-
13 Aug 2012 5:20 AM #2
I cannot reproduce this with 4.1.1+ dev code. Can you reproduce it with 4.1.1?
Search the forum: http://www.google.com/coop/cse?cx=01...%3Az7of1ufqccu
Read the docs too: http://extjs.com/deploy/dev/docs/
Scope: http://extjs.com/forum/showthread.ph...642#post257642
You found a bug! We've classified it as
EXTJSIV-6683
.
We encourage you to continue the discussion and to find an acceptable workaround while we work on a permanent fix.


Reply With Quote