Bug fixes

Didn't really intend to push another release as a number of the items I wanted to complete in the next release aren't there yet - however a number of minor bugs and a major issue with IE edge mean't it was better to release earlier.

Changes

• Column count is now from 1 not 0 for text cursor/caret position indicator (inline with other examples I can find in tools such as sublime).
• A new setContent method has been added to the Region element class allowing the content of any region to be updated dynamically from a DOM element or HTML string (thanks to @brunjick for input on this).

Bug fixes

• Fix for IE Edge (if someone can shed some light on what the hell is going on here and why my HACK/PATCH is needed that would be awesome (see here: #258) (thanks to @JNazarukPragmaticWorks for the report and additional testing/feedback).
• Fix for removing the beforeunload and unload handlers when destroying the editor (thanks to @brunjick for the report).
• Fix for _ordered_regions attribute not being reset in the EditorApp when syncRegions is called, caused the wordCount to double up each time the editor was start/stopped (someone did highlight this to me but I can't find where so thank you and apologise I can't credit you with the report).
• Update CSS example in the Getting started guide to fix an issue (thanks to @johnnylee for posting a fix).
• Fix for erroneous class attribute being added when converting an element to a heading.

Support for word count

Changes:

• Added support for word count (counts the number of words in the editable regions of the page), see bottom right in the inspector bar.
• Added support for text cursor/caret position (line, column) in preformatted text blocks, again see bottom right when cursor is in a preformatted section of text.

Fixes

• Fixed issue where target="" was applied to links without a target (thanks to @sbotting for the report).
• Fixed highlighting of regions being triggered accidentally when using shift key to switch browser tabs (thanks to @a-komarev for the report).
• Hacky fix for IE11 text cursor/caret visible through dialogs (thanks to @themoor88 for the report).

Minor enhancements/fixes

Minor changes:

• Added support for pressing the return key on images or videos to generate a new paragraph (thanks to @a-komarev for his input on this and the following item).
• Added a default empty placeholder for text elements of '...' and support for setting the placeholder value via data-ce-placeholder.
• Added support for initializing the editor without the ignition component via the new withIgnition argument (thanks to @a-komarev, @afzaalace for input on this feature).
• Added exports to module to support for require with browserify (thanks to @yaplusplus for requesting this).

Minor fixes:

• Deleting an image or video with delete key no longer also deletes the first character from the next text element (thanks to @damiansb for reporting the issue).
• Paragraph elements are now the default element for empty regions not H1s, this was an accidentally change left in from testing in the last release (thanks to @a-komarev for reporting this).
• Fix for Command + Paragraph tool not creating a paragraph after a preformatted block in WebKit browsers on OSX, thanks to @themoor88 for reporting this issue and follow up details, thanks to @jonolock91 for providing additional feedback).

Minor enhancements/fixes

This is a minor release with some enhancements and bug fixes.

Minor changes

• Updated the init method so that it doesn't bail if there's no editable regions, instead the ignition switch is simply hidden or shown based on the presence of regions (thanks for @oodavid for highlighting this).
• Added !default flag to SASS settings (both in ContentTools and ContentEdit) (thanks to @vudaltsov for requesting this).
• Made it easier to modify the placeholder element used when a region becomes empty via a new editor method createPlaceholderElement, see details here: #180 (thanks to @ richardprice for requesting this).

Minor fixes

• Fix for shift+enter short-cut not triggering a taint event which prevented the line-breaks being saved (thanks to @shawnlehner for reporting this).
• Fixed issue where images with a border radius had their selectable region and edges (for resizing) modified so that it wasn't always possible to resize them or select them as expected (thanks to @oodavid for reporting this).

Making progress on Fixtures

This release provides a working demo of fixtures within the sandbox along with a number of updates to the Editor, Tools and Inspector to accommodate the nature of fixtures vs. freely editable content.

There's no documentation yet (to be provided for the end of the month) and I still don't recommend using Fixtures in a production environment (though I'm going to be doing just that!) However if you do have the urge to experiment with them your feedback and bug reports are very welcome at this early stage.

Minor changes

• Add a new editor method syncRegions which allows you to sync the editor with the page, for example if you add a new region dynamically.
• Added support for specifying the function used to determine if a region is a fixture, by default the editor looks for the attribute data-fixture.
• Updated the canApply method for tools that can't be applied for fixtures.
• Updated the inspector to exclude fixtures from the tags that can be inspected.
• Added a fixture to the sandbox demo (the title element).

Minor fixes

• Fixed issue #203 where classes weren't removed from text elements when the type of element was changed (thanks to @andreygolovin for reporting this).

Introduction of `ContentEdit.Fixture`

This release provides a couple of minor fixes/updates and introduces any early version of the ContentEdit.Fixture.

Minor fixes/updates

• Fix for unbinding ContentEdit events when the editor is destroyed, thanks to @andreygolovin for identifying and pushing a patch for that.
• Modified the StylePalette.styles method to accept an element instead of a tag name so that the method can be overridden to support more complex filters.

Introduction of fixures

Fixtures provide standalone fixed position editable elements, for example you adding a H1 to your news article page that cannot be removed or dragged somewhere. This release is a very early release and use of fixtures is for the brave right now (lots of changes/improvements to come). The next release will see the tools in ContentTools updated to respect the can method for elements (e.g preventing you from removing an element using the delete tool if can('remove') returns false. There's a little more information about fixtures in the ContentEdit release notes here: https://github.com/GetmeUK/ContentEdit/releases/tag/1.1.2

1.2.3

I'd hoped to be a little further along by now but unfortunately fixture/standalone type elements (elements without regions) are not stable yet and there were some pressing bug releases to push.

Minor bug fixes:

• Fix for IE link UI dialog not appearing (thanks to @wrencH13 for the code to fix this).
• Fix for cloudinary image uploader template - incorrect event handling code (thanks to @themoor88 for fixing this one).
• Fix for pasting content in IE (again thanks to @wrencH13 for fixing this one).
• Fix for videos/iframes with long src values (thanks to @Eeliya for spotting this).
• Fix for creation of orphan elements in empty regions on save (thanks to @sticklvl for reporting this one and providing a hint to the problem).
• Improved handling of end of content line returns in Pre text elements (think I finally cracked this hack now - wish I didn't have to though!)

I've also added a quick update to the README to hint at where it's best to post different things for ContentTools, I'd like to move some of the more common questions over to StackOverflow. I check SO daily and the community is just bigger than the projects repo community and better able to help with some of the questions that get posted as issues currently. Anyway if you have any questions about this or feedback let me know via gitter or email me direct [email protected].

1.2.2

• Updated to release 1.1.0 of ContentEdit which adds support for behaviours.
• Improved the Toolbox.tools method so that updating tools no longer remounts the toolbox.
• Fixed a bug where the code tab in the properties dialog could be selected even when muted (e.g when an image's properties where being inspected).
• Improved the handling of issue #58 for pre-tags (though this is still a hack and a better solution is planned).

Note: The ContentTools editor does not yet respect element defined behaviours but work on this is underway as part of the on-going work on issue #79 and should be in place in the next release.

1.2.1

• Adds support for bower installs (thanks to @toastercup)
• Adds support for configuring CSS class names for alignment of text and elements.
• Adds support for region ready event.
• Fixes editor revert action not reverting the page HTML.
• Fixes imageuploader.fileready event not sending through file information with the event.

New event model

Release 1.2 sees the following changes, some of these are unfortunately not backwards compatible and may break existing integrations:

• New event system (based on native DOM event system), this will see bind, unbind and trigger methods against UI components replaced with addEventListener, dispatchEvent, removeEventListener (potentially breaking existing code).
• New events will be added for the UI including start and stop events for the editor.