Mailing List Archive

// Add your reply above here
==================================================
theory updated this ticket at March 16th, 2011 @ 07:54 PM
* Milestone changed from "2.0.1" to "2.0.2"
* State changed from "resolved" to "open"

--------------------------------------------------------------------------------

Assigned: theory
State: open
Milestone: 2.0.2
View this ticket online: http://bricolage.lighthouseapp.com/projects/29601/tickets/217-xinha-wysiwyg-fields-broken-when-collapsed-on-load

Stop being notified of this ticket's changes: http://bricolage.lighthouseapp.com/projects/29601/tickets/217-xinha-wysiwyg-fields-broken-when-collapsed-on-load/watch
Update your Profile: http://bricolage.lighthouseapp.com/profile
Support: support@lighthouseapp.com or http://help.lighthouseapp.com

// Add your reply above here
==================================================
Nick Legg updated this ticket at March 17th, 2011 @ 12:07 PM

Is it safe to assume that a newly created element will always have the highest element id?

I have attached a (very unclean) patch that boots Xinha on the element with the highest id every time Container.refresh() is called. This is called by addElement(), deleteElement(), and copyElement(). We really only want Xinha to boot on toggle() and addElement() but unfortunately the new element isn't created until after that call completes (the magic is asynchronous). Still testing here, but it's working for us so far.
--------------------------------------------------------------------------------

Assigned: theory
State: open
Milestone: 2.0.2
Assets:
- new_element_xinha.patch http://bricolage.lighthouseapp.com/projects/29601/tickets/217/a/963798/new_element_xinha.patch


View this ticket online: http://bricolage.lighthouseapp.com/projects/29601/tickets/217-xinha-wysiwyg-fields-broken-when-collapsed-on-load

Stop being notified of this ticket's changes: http://bricolage.lighthouseapp.com/projects/29601/tickets/217-xinha-wysiwyg-fields-broken-when-collapsed-on-load/watch
Update your Profile: http://bricolage.lighthouseapp.com/profile
Support: support@lighthouseapp.com or http://help.lighthouseapp.com

// Add your reply above here
==================================================
Nick Legg updated this ticket at March 17th, 2011 @ 12:40 PM


--------------------------------------------------------------------------------

Assigned: theory
State: open
Milestone: 2.0.2
View this ticket online: http://bricolage.lighthouseapp.com/projects/29601/tickets/217-xinha-wysiwyg-fields-broken-when-collapsed-on-load

Stop being notified of this ticket's changes: http://bricolage.lighthouseapp.com/projects/29601/tickets/217-xinha-wysiwyg-fields-broken-when-collapsed-on-load/watch
Update your Profile: http://bricolage.lighthouseapp.com/profile
Support: support@lighthouseapp.com or http://help.lighthouseapp.com

// Add your reply above here
==================================================
Nick Legg updated this ticket at March 17th, 2011 @ 12:45 PM

Well, that uncovered another bug with WYSIWYG loading. If you have a WYSIWIG open, then you add or delete any other element, the WYSIWIG (Xinha in particular here) shuts down and does not re-initialize. As such, I re-re-engineered my patch to reboot all WYSIWIGs on Container.refresh().
--------------------------------------------------------------------------------

Assigned: theory
State: open
Milestone: 2.0.2
Assets:
- new_element_xinha.patch http://bricolage.lighthouseapp.com/projects/29601/tickets/217/a/963877/new_element_xinha.patch


View this ticket online: http://bricolage.lighthouseapp.com/projects/29601/tickets/217-xinha-wysiwyg-fields-broken-when-collapsed-on-load

Stop being notified of this ticket's changes: http://bricolage.lighthouseapp.com/projects/29601/tickets/217-xinha-wysiwyg-fields-broken-when-collapsed-on-load/watch
Update your Profile: http://bricolage.lighthouseapp.com/profile
Support: support@lighthouseapp.com or http://help.lighthouseapp.com