29 Jan
2010
29 Jan
'10
4:24 p.m.
Marta Girdea wrote:
On Fri, Jan 29, 2010 at 3:04 PM, Marius Dumitru Florea
<
mariusdumitru.florea(a)xwiki.com> wrote:
Not necessarily. Take for instance XWIKI-4665. I think the user should
be able to jump to a page even when in edit mode as long as the focus is
not on the rich text area. When the focus is on the rich text area the
shortcut key is triggered for the inner (edited) document and the jump
to page feature should be disabled.
XSKINX-14 could be a solution if the inner (edited) document were loaded
with a different action (right now the action is edit).
Thanks,
Marius
Hi devs,
Right now JavaScript extensions are included when a document is rendered
in WYSIWYG edit mode. This has both advantages and disadvantages.
Pro: If the output of a macro depends on a JavaScript extension, then
the result of rendering that macro will be the same in view mode and
(WYSIWYG) edit mode.
Con: If the JavaScript extension is not aware of the edit mode then it
can modify the DOM document outside of the read-only macro markers which
leads to unwanted changes in the content of the edited document (i.e.
the modifications done by the JavaScript extension are saved). Such an
example is http://jira.xwiki.org/jira/browse/XWIKI-4665 .
Would XSKINX-14 (Let extensions declare a list of web actions (view, edit,
etc.) it should be pulled for) fix at least some of the issues? WDYT? Should we limit the WYSIWYG in order to
make the editing safer?
I'm +0.
Thanks,
Marius
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs