Skip to content

Latest commit

 

History

History
614 lines (396 loc) · 45.7 KB

CHANGES.md

File metadata and controls

614 lines (396 loc) · 45.7 KB
Raw

Change Log

2017-xx-yy: v2.13.0

2015-09-07: v2.12.0

  • New logo! Created by Austin Anderson and chosen by the Markdown Here users, our great new logo is finally ready for action.

    • Much thanks to Austin for his work polishing and tweaking the 60 variants of the logo. He did a lot of work getting things just right.
    • Thanks to everyone else who submitted a design: Rafe Goldberg, Jack Reis, Enrique Esquinas, Leon Wilmanns. All of their designs were great and I would have been happy for any of them to win.
    • Seriously, if you haven't seen the other designs, go check them out. And then check out their portfolios, bookmark them, and contact them the next time you need design work done.
    • Thanks to all of you who took the time to vote for the new logo.
    • If you are unhappy with the change to a monochrome browser toolbar and context menu button, +1 this issue.

  • Fixed bug #297: Unrendering an email that is a reply to an email that was itself rendered with MDH would fail (if the original email were visible, like with Thunderbird or when it's expanded in Gmail).

    • Thanks to Dave Tapley for creating a great video that illustrated the problem and how to reproduce it.
    • Repeatedly triggering this bug could also lead to the next bug...

  • Fixed bug #289: With forgot-to-render detection enabled, sending a large email could result in MDH causing the mail client to hang.

  • Fixed bug #283: Forgot-to-render detection was broken for Google Inbox. Thanks to Marvin R..

    • If you find that the forgot-to-render detection gets broken for the Gmail or Google Inbox web interfaces, please post to the "markdown-here" Google Group or create an issue in the Github project. The MDH code that hooks into the webmail UI is brittle and might break when Google changes stuff.

  • Fixed bug #288: Some character combinations involving a dollar sign in inline code would render incorrectly.

  • Updated and new translations:

2015-05-26: v2.11.9

2015-05-21: v2.11.8

  • Fixed bug #251: Improved HTML-to-plaintext processing, in order to make newline handling better. Fixes some cases where tables get messed up. Thanks to hchaase.

  • Fixed bug #241: Rendering was very slow on Chrome Beta and Canary. Thanks to Alex Vaystikh.

  • Fixed Pale Moon compatibility. Thanks to Ismani Nieuweboer.

  • Partially fixed bug #104: Pre-rendered links (especially auto-links) in code were getting converted to Markdown when rendering (so you end up with raw Markdown in your code). This is now fixed for backtick-style code (inline and block), but not for indented code blocks.

  • Updated translations:

2015-04-06: v2.11.7

  • No user-facing code changes. Modifications to pass Mozilla review. (Added a preprocessor to strip out cross-browser code.)

2015-03-29: v2.11.5

  • Fixed bug #243: Due to the way paragraphs were styled, there appeared to be a "blank line" inserted at the top when your Markdown-Here-rendered your content. The styling was changed to correct this.

  • Changed styling of sub-ordered-lists to match Github's: Top level is still numbers, first sub level is Roman letters, second sub level is Roman numerals. Will make your email lists look totally pro.

  • Fixed bug #237: Made Mozilla preferences handling more robust. Helps to deal with non-ANSI characters, synchronization, and corruption.

    • Thanks to flying-sheep for reporting the corruption problem and helping to diagnose it.

  • Added and updated translations:

  • And thanks to Erin for looking after Wulfie long enough for me to put this release together.

2015-02-16: v2.11.4

  • Fixed bug #233: Reference links were broken if the URL part was pre-formatted.

  • Added forgot-to-render check support for "Inbox by Google".

  • Updated translations:

2014-11-10: v2.11.3

2014-09-18: v2.11.2

2014-08-31: v2.11.1

2014-05-17: v2.11.0

  • Added ability to de-render after saving. After you render and save an email draft or an Evernote Note or a Google Group post or a Blogger post (or etc.), you can go back, edit it, and de-render it back to Markdown.

  • Added a partial Korean translation, thanks to dotvezz.

    • Do you speak something in addition to English? At least half of all Markdown Here users are not English, but Japanese is the only complete translation we have. It's easy to help with translations -- just try out the Crowdin project for Markdown Here. Thanks!

  • Added ability to disable GFM line breaks.

  • Fixed bug #51: Links with URL text (like [http://example.com](http://example.com) weren't rendering properly.

  • Altered default H1 and H2 header styles to match new GitHub styling. You'll have to click "Reset to Default" to get these styles.

  • Fixed bug #173: Markdown Here was generating lots of errors in the console on sites with an iframe that use tight security (like jsbin.com). Thanks to Devin Weaver.

2014-01-29: v2.10.0

  • Markdown Here has been translated into Japanese! It's also ready to be translated into your language, so please take a look at CONTRIBUTING.md and our Crowdin project. Getting involved is super easy.

  • The automatic addition of anchors to headings is now an option and disabled by default. Guido Hoermann quite rightly pointed out that it creates annoying visual noise in Thunderbird. It's probably not used enough to justify being enabled by default, and it's very easy to re-enable it (bottom of the options page).

  • The "forgot-to-render" check that was added in version 2.9.2 is now enabled by default. As always, please file a bug or otherwise report if you have any problems or suggestions for improvement.

  • Markdown Here now works with older versions of Chrome and Chromium. (Tested on version 24 and 25, which didn't work before but do now.)

    • Thanks to Dustin Engstrom for providing the fix for this (and for submitting the first MDH code pull request!). Thanks to Adam Kruger for reporting the problem.

  • Fixed bug: In Chrome, options page link in upgrade notification was no longer working.

2013-11-07: v2.9.4

  • Updated Highglight.js, which is the syntax highlighting library used by Markdown Here.

    • New languages: Handlebars templates, Oracle Rules, F#, AsciiDoc, Lasso, SCSS, VB.NET, Mizar.
    • New themes: Docco, Foundation, Mono Blue, Monokai Sublime, Obsidian, Railscasts.
    • And lots of theme and language improvements.
    • This resolves MDH issues #59 and #114. Thanks to Alex Pacini and Robert Jeppesen for reporting them.
    • Make no mistake, all credit for this goes to Ivan Sagalaev and the Hightlight.js contributors.

  • Added some debug logging to help diagnose issue #141. (And maybe fixed that issue, but probably not.)

2013-10-27: v2.9.3

  • New feature: Added support for smart arrows. Here's how to use them:

    • <-- ←
    • --> →
    • <--> ↔
    • <== ⇐
    • ==> ⇒
    • <==> ⇔

  • Fixed bug: Options were broken in Safari 7 (the Mavericks version).

  • Fixed bug: In Thunderbird (mostly), raw HTML was not rendering properly. This is caused another bug: using angular brackets makes contents invisible.

2013-10-18: v2.9.2

  • Feature/fix: You may have found out the hard way that if you render, then make changes, and then unrender, you lose the changes. Now Markdown Here will warn you when unrendering will cause you to lose changes, and give you the choice of proceeding or not.

    • Due to JavaScript support differences, this feature is not supported in Postbox or Safari 5 (but it is supported in Safari 6+).
    • Thanks to jakov for originally requesting this change, and to jdhines and lihlii for also reporting/requesting it.

  • Fixed bug, for real this time: In Chrome, for some users, the Markdown Here upgrade notification would show up every time they opened Chrome.

    • Thanks again to Chris/jhwarehouse for reporting the bug still existed and helping to sort it out.

  • Fixed bug: Raw Markdown in rendered code blocks is detected by forgot-to-render check.

    • Thanks to Menno Smits for reporting the bug and helping to investigate.

  • Fixed bug: In Thunderbird, the new forgot-to-render check was incorrecting triggering on rendered links and headers.

2013-10-11: v2.9.1

  • Fixed bug: If a bad language name was used for a code block (where "bad" might even just be "SQL" vs. "sql"), rendering would break. Language name case is now ignored.

  • Fixed bug: Markdown Here wasn't working on Postbox. Thanks to Branden C. for letting me know.

  • Fixed bug: In Chrome, for some users, the Markdown Here upgrade notification would show up every time they opened Chrome. (I couldn't reproduce it myself, but the notification display is less aggressive now.)

  • Fixed bug: In Chrome, memory was leaking. The size of the leak was proportional to the number of tabs and how long they were left open.

    • I mitigated this in the Markdown Here code, but... it looks like it might actually be problem with Chrome itself. If someone familiar with Chrome/Chromium code and extension behaviour could help me I'd appreciate it. Here's a Github Gist I created that replicates the problem.
    • Thanks to Thomas Broyer for reporting this problem.

2013-10-07: v2.9.0

  • New feature: Forgot-to-render detection. Have you ever forgotten to make your Markdown pretty before sending your email? Me too. Now Markdown Here will detect when your email contains raw Markdown and will give you second chance to go back and render it before sending.

    • This feature is supported in Thunderbird (and Postbox), and for Gmail in Chrome, Firefox, Opera, and Safari. (Pull requests welcome for Hotmail, Yahoo, etc.)
    • For now this feature is off by default because I'm nervous about too many false positives driving people crazy. But please opt in! The checkbox to enable it is at the bottom of the MDH Options page. And please give feedback on how the feature does or doesn't work for you, either in the Github issue or the MDH Google Group.
    • Thanks to Petr Pudlák for requesting this in issue #90, Zhou Qiang in issue #96, Adam Backstrom in issue #98.

  • Compatibility improvements!

    • Now works great with Blogger (details).
      • The changes made will probably help with some other sites. If you tried out a site before and ended up with empty lines in your code blocks, try it again.
      • See the Compatibility wiki page for details.
      • Thanks to lambdaalice for reporting the previous bad behaviour in issue #89.
    • Now works very well with Wordpress (details).
    • See the Compatibility wiki page for even more places where Markdown Here works, like Google Sites and Facebook Notes.

  • New feature: Automatic anchors for headers. This makes it much easier to put a table of contents (or other intra-page links) inside your email or blog post. Just use the text of your header as the anchor link text. For example:

    [See below](#Deep-Dive Details Section) for details.
...
Deep-Dive Details Section
=========================
...
    • Thanks to Casey Watts for requesting this and giving insight on how to do it. Closes issue #93.

  • Chrome and Firefox: Options page no longer opens when Markdown Here updates. Now there's a little notification in the corner of the window that can be clicked to show the MDH Options page (and the changes in the release), or dismissed.

  • Added the ability to set site-specific styles. To see an example of how to do this, either reset your Primary Styling CSS or take a look at the source for it.

  • Fixed bug: Math: single-character formula won't render.

  • Fixed bug: [a](b) links shouldn't expand inside of a code block.

    • Thanks to Dan Brown for reporting this bug.

  • Fixed bug: "Smart" quotations and apostrophes would sometimes get confused and curl the wrong way.

    • Thanks to Jay Dixit for reporting this bug.

  • Fixed bug: Shouldn't require blank line before list.

2013-08-24: v2.8.2

Added support for Opera! Get it here.

2013-06-23: v2.8.1

PLEASE NOTE: If you've never customized your CSS, you should click the "Reset to Default" button for the "Primary Styling CSS". This will fix a bug (see below) and maybe give you better styling (if you installed MDH before version 2.7.0, Feb. 2013). If you have customized your CSS, you can take a look at the changes to the default CSS and decide what to take. A more elegant way of handling this is being planned.

  • The designer/artist of the Markdown Here logo has her own website up. You should check it out! http://tatianafryntoff.com/

  • Fixed bug: Pre-formatted links break Markdown links.

    • Thanks to users Mitchell W. and crdx for reporting this bug.

  • Fixed bug: MD links should automatically add schema.

  • Fixed bug: Firefox/Thunderbird: Code blocks with horizontal scroll would have bad background colour.

    • Thanks to user Hans B. for reporting this bug.
    • Note that to get this bug fix, you either need to reset your "Primary Styling CSS" to default, or manually apply the fix.

  • Fixed bug: Inline code line breaks are lost.

    • Thanks to user CheechGe for reporting this bug.

  • Fixed bug: Sometimes options page MD preview doesn't initially render.

2013-05-19: v2.8.0

2013-03-05: v2.7.3

  • Fixed Firefox+Linux bug (#56): Toolbar button icon was not displaying correctly.
  • Fixed Firefox bug: Toolbar button would not stay removed when browser was restarted.
  • Added support for Icedove (Debian version of Thunderbird).

2013-02-17: v2.7.2

  • Pre-formatted links will now be retained. If you use your email editor's formatting controls to create a link, it will be retained when you toggle the Markdown Here rendering state.

  • Firefox/Thunderbird: Fixed bug; Resetting the primary stying CSS wasn't working.

2013-02-13: v2.7.1

  • Under-the-hood changes to satisfy Mozilla requirements.

2013-02-06: v2.7.0

  • Markdown Here has a new logo! A big thank you to the talented Tatiana A. Fryntoff for creating our shiny new logo.

  • Support for new Markdown features. All credit goes to chjj, the maintainer of the Marked library.

    • Tables! Now you can easily add tables to your email with Markdown. If you're not familiar with the syntax, check out the wiki cheatsheet. This closes issue #13.
    • Strikethrough: Put double tildes around things to strike it out (~~strike it out~~).
    • Smarter lists: Have you ever had a numbered list mysteriously/annoyingly become a bullet list because it comes after one? Not anymore.
    • GFM line breaks: If you put a line break in your Markdown, it will be a line break after you toggle, instead of joining to form a single line. This closes issue #12.

  • Added a Markdown Toggle button to complement the context menu item and hotkey.

    • In Chrome and Firefox, this button will appear on the browser toolbar. It will be enabled when you're typing in a compose box that Markdown Here can work with.
      • You might notice the button enabled when you're typing in places other than your email page -- try it out! You might discover that Markdown Here works somewhere new. If you do, please add it to the compatibility wiki.
    • In Thunderbird and Postbox the appears on the formatting toolbar.
    • In Firefox, Thunderbird, and Postbox you can add/remove/move the button by right-clicking on the toolbar, clicking "Customize", and then dragging the button around. In Chrome you can remove it by right-click on it.
    • If you have any feedback about the new button, please join the "markdown-here" Google Group discussion.
    • Thanks to user jakov for suggesting this feature in issue #34.

  • Default styling changes. Note that you'll have to reset your styles to get the new defaults (click "Reset to Default" on the options page). The changes include:

    • Slightly smaller header font size.
    • Less space between list items.
    • Link styling is now more standard (e.g., underlines in Gmail).
    • If you have any feedback on the default styling, please join the Google Group discussion.
    • Thanks to Casey Watts for his input.

  • Added a "Basic Usage" section to the options page. This is in response to a tweet from user KSuzukii.

  • Yahoo and Hotmail/Outlook.com now work a bit better.

2013-01-02: v2.6.4

  • Firefox/Thunderbird: Actually fixed the bug that I thought I fixed in v2.6.3. Much thanks to Daniel Ashton for letting me know that it was still busted and John Galt for assisting in the fix.

2012-12-01: v2.6.3

  • Firefox/Thunderbird: Fixed bug: Changes in Firefox/Thunderbird version 17 resulted in the options page not working correctly.

2012-10-06: v2.6.2

  • Firefox/Thunderbird: Fixed bug: Tabbing into the email body and then Markdown-Toggling via keyboard (i.e., never clicking the mouse in the message body) would result in the email body being lost when sent.

  • Discovered Wordpress post compatibility, thanks to user Sina Iravanian. (See details.)

2012-09-09: v2.6.1

  • Added hot-key (keyboard shortcut) support. The default key combination is ctrl+alt+m, but it is configurable from the Markdown Here options. Using the hot-key is identical to using the "Markdown Toggle" context menu item.

  • Added basic support for the Postbox desktop email client, at the request of a user. There are some significant caveats, like the lack of an options page.

  • Fixed bug: Gmail and Thunderbird reply exclusion wasn't working well, resulting in quoted replies getting messed up when doing a full (non-selection) rendering.

  • Fixed: In Chrome on OS X, right-clicking on a word causes it to be selected. If "Markdown Toggle" were then clicked, it would render just that one word, which is lame. This behaviour is now avoided by not rendering single word selections -- if a single word is selected, the entire content will be rendered instead.

  • Discovered Evernote web-interface compatibility, thanks to user markgoodson. (See details.)

2012-08-29: v2.6.0

  • Added support for TeX math formulae. For info check out the Options page.

    • Note that this feature is disabled by default, due to privacy concerns. Again, the see the Options page for info.
    • Thanks to bordaigorl for suggesting this feature and helping to implement it.

  • Firefox/Thunderbird: Added Options page. (Chrome already had it.) Take a look around and play with the styles.

  • Added a few new syntax highlighting themes. (Thanks to Highlight.js.)

2012-08-16: v2.5.3

  • Chrome: Fixed compatibility with Chromium v18 (currently the version in the Ubuntu repo).
    • Limitation: Chromium v18 doesn't support synchronized settings. And when the user upgrades to a more recent version that supports chrome.storage, previous settings will not be migrated.
    • Thanks to gingerlime for finding this bug and helping to fix it.

2012-08-08: v2.5.2

  • Firefox/Thunderbird: Minor change resulting from Mozilla review. (Fixed a "loose" variable.)

2012-08-02: v2.5.1

  • Chrome: Fixed bug: In version 21 of Chrome, the Markdown Here options page no longer rendered correctly. (Chrome changed the display style name for flexbox layout from "-webkit-flexbox" to "-webkit-flex". Using bleeding edge CSS maybe wasn't a great idea.)

2012-07-27: v2.5.0

  • Changed default styles (e.g., font sizes) to be more relative. This results, for example, in ordinary Markdown-Here-rendered text looking more like ordinary Gmail text instead of the previous somewhat jarring size change.

    • This also fixes a bug: Inline code in headings will now be the correct size.

  • Chrome: Options page with changelist at top will be opened when Markdown Here updates.

  • Significant changes under the hood to (hopefully!) allow Markdown Here to properly pass a full Mozilla review. For details, see issue #21.

  • Fixed bug: Empty line would appear at the top of rendered fenced code blocks that had been pasted.

  • Removed feature/fixed bug: Pre-formatted links are no longer left intact. It conflicted with Marked.js's GFM behaviour of turning text that looks like a URL into a link. So if a pre-formatted link was created that used the URL as the text (e.g. <a href="http://github.com">http://github.com</a>), the resulting rendering would get messed up (<a ...><a ...>...</a></a>).

    • Let this be a lesson about the perils of frivolous features.

2012-07-21: v2.4.0

  • Chrome: Added styling options. You can now edit the CSS used to style the rendered Markdown and choose between various syntax highlighting themes. These options are synchronized between your different installations of Chrome (if you have it enabled in Chrome).

  • Removed feature: Pre-formatted text (colours, italics, bold, etc.) and lists (made using the email client rich edit controls, for example) are no longer left intact. It just caused too many problems and special cases (and would have required more special cases to get working again in Yahoo). Links are left intact.

    • There are still two ways to still get additional formatting:

      1. Format after Markdown-Toggling. Note that any changes -- including formatting -- made to rendered text will be lost if you toggle back to Markdown. So only do your additional formatting after you're happy with the rest.
      2. Add inline HTML with the desired formatting.

        • In your Markdown, you can use <span> or <b>, etc., to explicitly style your text. For example:

          Here is some <span style="background-color:red; font-size:2em;">*big red*</span> highlighting.

        • If you find you use inline tags with complex styles a lot, edit the CSS in the options to add a class that you can reuse for your inline tags. For example, in the CSS add:

          .bigred {
  background-color: red;
  font-size: 2em;
}

          And then in your Markdown:

          Here is some <span class="red">*big red*</span> highlighting.

    • It saddens me to remove out this feature, but I think it's essentially creeping featurism that has a higher bug-danger-cost than it has an actually-useful-benefit. If this feature is/was important to you, please create an issue to let me know.

2012-06-20: v2.3.1

  • Fixed bug: Yahoo: Code blocks would just show a bunch of span tags. (Introduced in 2.3.0.)

2012-06-20: v2.3.0

  • Works with Google Groups posts! You can use it either in the GG rich compose box, or when sending posts via email.

  • Added support for inline, pre-rendered images. Some email editors allow the user to drag-and-drop an image into an email body, and some allow users to select one from their computer or the web (or an emoticon in the email compose controls!). Previously, the image would be lost when a "Markdown Toggle" was done. Now the image will be retained.

  • Pre-formatted text (colours, italics, bold, etc.), links, and lists (made using the email client rich edit controls, for example) are now left intact when rendering the Markdown.

  • Added ability to convert a reply email in its entirety, rather than using the select-and-convert piecemeal approach.

    • This doesn't work with Yahoo and Hotmail, because they don't seem to quote the original email.
    • Resolves issue #14.

  • Some styling changes.

  • Bug fixes.

  • Created a Markdown cheatsheet: https://github.com/adam-p/markdown-here/wiki/Markdown-Here-Cheatsheet

2012-06-07: v2.2.0

  • Syntax highlighting! Coloured monospace text is super sexy.

  • Email signatures are now excluded from conversion. Signatures must be preceded by "-- " (note the space at the end).

  • Fixed block quotes.

  • Much improved table and definition list styling.

  • Better styling and consistency across browsers and mail clients.

2012-05-31: v2.1.3

  • Firefox/Thunderbird: "Markdown Toggle" menu item will show up for non-rich-edit elements, but an error message will be given if the item is clicked. Hopefully this will help people notice that they're not using a rich editor, instead of wondering where the menu item is.

  • Chrome: If the "Markdown Toggle" menu item is clicked for a non-rich-edit element, a helpful error message will be shown.

  • Fixed bug: Significant trailing spaces were being stripped. This was breaking the Markdown syntax feature of two spaces at the end of the line indicating a hard line break.

  • Changed context menu access key to 'k'. Previously, Chrome had no access key and Firefox/Thunderbird had the more-common letter 'm'.

  • Other minor bugfixes.

2012-05-21: v2.1.2

  • Chrome: Fixed manifest. Using manifest version 2 worked in debug, but not when published to the Store. Had to delete original Store extension in the process. :(

  • Chrome: Updated manifest home page link to new Store address.

2012-05-21: v2.1.0

  • Added Thunderbird support to Firefox extension.

  • Tightened security restrictions in Chrome extension.

2012-05-20: v2.0.0

  • Added Firefox extension.

  • Chrome version: Moved most rendering code out of content scripts and into background scripts. This means less code needs to be loaded with each page. (The Firefox version also more or less behaves like this.)

2012-05-17: v1.2.1

  • Bug fix: Rendering and reverting same selection (rather than reverting a point or selection within the original selection) would result in a loss of original Markdown.

2012-05-16: v1.2.0

  • New feature: You can convert only part of an email by selected a region before clicking "Markdown Toggle". This is great for replies. To revert back to Markdown, right-click in the converted block and click "Markdown Toggle" again.

2012-05-15: v1.1.2

  • Fixed issue with fonts sent and received by Yahoo.

2012-05-14: v1.1.1

  • Fixed Gmail display of received rendered-from-Markdown email. Gmail was killing the <style> block, so styles are now also set explicitly on each element. Gmail works great now.

2012-05-13: v1.1.0

  • Added ability to revert rendered HTML back to Markdown.

2012-05-12: v1.0.0

  • Initial release.