Lines Matching full:editing
157 during editing, but will still be part of the document DOM. This can be used mainly
219 BUG-1578306</a>] The context menu was wrongly positioned if the editing document
227 Patch-1579507</a>] Firefox' spellchecker is now disabled during editing mode.
266 BUG-1598517</a>] Meta tags are now protected from execution during editing (avoiding
382 during editing (IE issue) and they don't interfere in other specific processors
416 BUG-1551734</a>] The SetHTML function will now update the editing area height no
417 matter which editing mode is active.</li>
523 BUG-1507953</a>] The editing area was getting a fixed size when using the "SetHTML"
592 BUG-1499708</a>] We now assume that, if a user is in source editing, he/she
690 editing area. Just define FCKConfig.EditorAreaCSS as an array of strings (each one
699 <li>The source view is now available in the editing area on Gecko browsers. Previously
701 <li><span>As some people may prefer the popup way for source editing, a new configuration
780 BUG-1178359</a>] Elements from the toolbar are not anymore draggable in the editing
788 an entry for it has been added to the editing area CSS, so you can customize with
998 BUG-1209093</a>] When "Full Page Editing" is active, in the "Document
1147 …source to remain untouched while editing or changing views. Just use the "FCKConfig.Prot…
1311 in the editing area. </li>
1316 BUG-1295526</a>] While editing on "FullPage" mode the basehref is
1335 to see the preview of the movie while editing, so a nice "placeholder"
1346 <li>The handles on form fields (small squares around them) and the inline editing
1376 <li>The preview now loads "Full Page" editing correctly. It also uses the
1587 to limit the editing area size. </li>
1617 page editing). The active "BaseHref" is also set to the preview window.
1661 editing must be enabled. </li>
1702 h1, etc...) to avoid differences from the editing and the final result. (Actually,
2014 <li>The editing area is not anymore clipped if the toolbar is too large and exceeds