cancel
Showing results for 
Search instead for 
Did you mean: 

Impossible to enter space in <input> within <htmlb:tableView>

guillaume-hrc
Active Contributor
0 Kudos

Hi,

Here is a strange problem.

I have developed some HTML bees in an Iterator, and the code looks like this:

      CLEAR html_str.
      CONCATENATE '<input id="'   p_cell_id
                  '" name="'      p_cell_id
                  '" size="'      '20'
                  '"maxlength="'  '20'
                  '" '
                 ' on_change="fireAJAX(this);"'
                 ' value='        l_str
                 '>'
      CREATE OBJECT html_bee.
      html_bee->add( html = html_str ).
      p_replacement_bee = html_bee.

With Ms Internet Explorer, I am unable to input space into those fields!! But it causes no problem with Firefox.

Any idea ?

Thanks in advance for your help.

Best regards,

Guillaume

PS: I had to change the 'on_change' because the forum didn't accept the event handler name

Message was edited by:

Guillaume Garcia

Message was edited by:

Guillaume Garcia

Accepted Solutions (1)

Accepted Solutions (1)

raja_thangamani
Active Contributor
0 Kudos

Guillaume,

I simulated the same . But I can able to enter the space in tableview iterator. Try to remove the onchange event & give a try...

Raja T

guillaume-hrc
Active Contributor
0 Kudos

Hi Raja,

I tried but without success.

What IE version do you use ? (we have 6.0.2900.2180.xpsp_sp2_qfe)

I am under the impression that the HTMLB framework might capture the Key Down event as there is code such as

on_keydown="sapUrMapi_InputField_keydown('Orders_3_3',event)"

in the classic <htmlb:inputField>

Thanks in advance.

Best regards,

Guillaume

raja_thangamani
Active Contributor
0 Kudos

Yes I to have the same IE Version <b>6.0.2900.2180.xpsp_sp2_qfe.070227-2300</b>

You can make use of Javascript events in HTMLB.

Look at the below blog where in I used those events..

/people/raja.thangamani/blog/2007/02/07/accomplishment-of-tab-and-auto-tab-in-bsp-part-i

<i>*Reward each useful answer</i>

Raja T

guillaume-hrc
Active Contributor
0 Kudos

Hi,

We found a workaround by simply adding the attribute

ct="InputField"

Thanks for your help, Raja.

Best regards,

Guillaume

Answers (0)