Hi David,
Before letting markItUp! go in the wild as an opensource project, I
used it for monthes in my personnal needs.I have implemented it in
many projects and moving the ID to the container saved me lot of time
in some advanced implementations.
It's mostly matter of CSS styling/conflicts and multi-instances
handlings.
Some examples:
#markitup {
position:absolute;
top:10px; left:10px;
}
Or and most important
#myHtmlEditor .markItUpButton1 {
/* ... an icon */
}
#myBbcodeEditor .markItUpButton1 {
/* ... an icon */
}
I agree and i am the first one to claim that it might seem
surprising.
Changing the identity and type of a element is not really elegant but
never bring me any problem so far.
I was certainly trapped with a specific advanced need the day i
decided switching the ID was necessary.
Now, i can't really remember why it was so important at the time. I
was certainly wrong on that one.
I will run some tests and obviously remove it from the next releases
after balancing pros/cons.
I assume the best solution is to give it as an option.
Thanks guys for the great feedbacks.
Regards,
Jay
On 3 avr, 15:24, "Richard D. Worth" <[EMAIL PROTECTED]> wrote:
> Jay,
>
> I'd be interested to hear some specifics on why you found it necessary to
> remove a unique identifier from an element, and put that on a different
> element. That's changing the identity and type of that element. Quite
> frankly, this is obtrusive, and surprising. Maybe there's an option you
> haven't considered. Or maybe you'll teach me about a difficulty I'm not
> currently aware of. Thanks.
>
> - Richard
