wagtail: TableBlock with custom TabbedInterface
When new TableBlock is used with default TabbedInterface - all works fine:
from wagtail.contrib.table_block.blocks import TableBlock
from wagtail.wagtailadmin.edit_handlers import StreamFieldPanel
from wagtail.wagtailcore.fields import StreamField
from wagtail.wagtailcore.models import Page
class TestPage(Page):
content = StreamField([
('table', TableBlock()),
])
search_fields = Page.search_fields
content_panels = Page.content_panels + [
StreamFieldPanel('content')
]
I see editor as expected:

But when I try to create custom TabbedInterface:
from wagtail.contrib.table_block.blocks import TableBlock
from wagtail.wagtailadmin.edit_handlers import StreamFieldPanel, TabbedInterface, ObjectList
from wagtail.wagtailcore.fields import StreamField
from wagtail.wagtailcore.models import Page
class TestPage(Page):
content = StreamField([
('table', TableBlock()),
])
search_fields = Page.search_fields
editor_content_panels = [
StreamFieldPanel('content')
]
edit_handler = TabbedInterface([
ObjectList(Page.content_panels, heading="Default Editor"),
ObjectList(Page.promote_panels, heading="Promote"),
ObjectList(Page.settings_panels, heading="Settings", classname='settings'),
ObjectList(editor_content_panels, heading="Editor"),
])
After creating new page with TableBlock and re-opening it for edition - table editor don’t appears:

But… After opening “Developer Tools” (F12) magic happens:

I’ve checked this bug with latest Chrome and Firefox. Looks like some JavaScript window refresh is needed on Tab click event.
About this issue
- Original URL
- State: open
- Created 10 years ago
- Reactions: 1
- Comments: 16 (7 by maintainers)
Oh, 2 hours spent and I finally found the solution:
It works for TableBlock and my MarkdownBlock.
@BertrandBordage 's fix helped, but didn’t work for me when the second tab is the active one when the page loads (on Chrome - Firefox was fine). I got this to work, but it’s very ugly:
There has to be a better way.
as a very fast and dirty workaround I’ve used
$(window).resize();called in the right moment is the answer. You can verify this by navigating to the tab where table is expected to be shown and calling this code from console (or simply resize window manually).@Proper-Job We’re using Bootstrap’s tabs module, so the events should be as described here: http://getbootstrap.com/javascript/#tabs-events