PDA

View Full Version : Textarea and its container getting indented leftmost and distorted on Pageup key



akj504
22 Sep 2014, 4:06 AM
Hi All,

I have a Textarea (Ext.layout.component.field.TextArea) with normal config in a container. If I press pageup key from within the textarea after entering sometext the entire contents of the container including textarea shift to the left, and only half of each fields is visible. Also there is no horizontal scrollbar getting introduced at bottom.


This is happening only with pageup key, not with pagedown or any other key.
Also if no text is entered in textarea, issues is not faced.
There are no keyevent handlers added to the textarea.


What could be the issue. Has anyone faced a similar issue anytime.

I am not sure how to debug it as nothing unusual is seen in console?


Thanks in advance.

slemmon
22 Sep 2014, 9:50 PM
Hi,

Can you share a test case that demonstrates the issue either here or at https://fiddle.sencha.com?
Also, what version of ExtJS are you working with?
On what browser / OS are you testing where you see the issue?

akj504
23 Sep 2014, 12:24 AM
docs.sencha.com/extjs/4.1.0/

Issue occurs only in Chrome - ver 37.0

Issue is not replicable in FF.

akj504
23 Sep 2014, 1:10 AM
Looks like its more specific to HTML/CSS on Chrome and not ExtJS.

http://jsfiddle.net/ARQ35/

But still can any expert here help me with this problem.

In the above fiddle, all fields are shifting to left on PageUp.

For my case, as I do not have much of margin on the left side, the all fields gets cut on the leftmost.


Thanks again.

slemmon
23 Sep 2014, 3:16 PM
Hi,

I'm not seeing in this fiddle that you're using ExtJS. Am I just missing where it's used in your fiddle?

akj504
24 Sep 2014, 1:21 AM
Yes agree, its nothing to do with ExtJS (but run the fiddle (http://jsfiddle.net/ARQ35/) as indicated & see the behavior)

As I wrote:

Looks like its more specific to HTML/CSS on Chrome and not ExtJS.
But still can any expert here help me with this problem.

On researching a bit more, I also found that the issue is a Chrome Bug (https://code.google.com/p/chromium/issues/detail?id=60472)

But still, can any expert here help me a Workaround that solves this problem