It's not a bad idea, but it's not a fix really. If the immediate parent doesn't move but the input does you have the same problem. For example, let's say you have this:
<div> <input> <input> </div> And both have overtexts and validation. The validation will push down the second input anyway. The point here is that you have to be mindful of how the component works. The fix is quite easy to implement (a line of css and wrapping your inputs). Your suggestion isn't a bad one, but I don't like polluting someone else's DOM. Setting an inline style when no position is set would likely suffice most of the time, but then someone would dynamically add a class to that parent and wonder why the positioning was out of whack... On Tue, Sep 13, 2011 at 12:02 PM, batman42ca <[email protected]> wrote: > It just occurred to me why Overtext works this way and it has > everything to do with the way CSS absolute positioning works. It's > only absolute relative to the nearest relatively positioned parent. > > BUT, why can't Overtext simply check the position of the parent? If > the immediate parent is not absolutely positioned and not relatively > positioned, make the parent relatively positioned. Wouldn't that be a > good way to deal with this? >
