We are setting a editor to be 100% width via css due to the known issue below. Which works but the "edit field" does not get 100% width and therefore you can only touch a portion of the control to get it to focus. When you set the 2nd line to 100% then when you type in the field the text does not appear on the screen. Since we are using the ASP.NET MVC wrappers to build the control it is being wrapped in a span. What is the best way to get this control to function properly with 100% width via css since you cannot pass "100%" to the width property of the MVC Wrapper??
.ui-ig-edit {width: 100% !important; height:25px;}
.ui-ig-edit > .ui-igedit-field {width: auto !important; text-align:left !important;}
This is from the known issues:
Width and height options can be set only absolutely (in pixels) under certain conditions
If the editor’s base element is not an <input> or <textarea> element and buttons, theme, or renderInContainer options are enabled, then the width and height options can be set only absolutely (in pixels).
Workaround
Thanks for escalating things. I look forward to hearing from you today!
Hi Tammy,
I am still waiting to hear from our developers and I have raised this with our Product Management team so this will receive some more attention.
I will have another update for you tomorrow.
I am still waiting to hear back from our developers on this.
The reason the text disappears is because the input is too long when the clear button is included. This is forcing the input (and the text in it) to render on another line, which is out of view.
I am currently discussing with our developers how we can get around this part of the issue. One workaround for now, would be to not use the any button types. And if you would still need the clear button, you could add an additional button manually to clear the text when clicked.
I will have more information on this for you tomorrow.
Yeah I think I was mistaken there. If you change it to 99% though and shrink the screen you will see the issue where the text disappears from the edit. If we could fix that then I could go back to how I originally did this if it makes more sense to go that way.