Issue with CKE 3.6.2 and image borders

I've had 3.6 running on my main project site for a while, works fine - I've got 3.6.2 running on a test environment, also works fine.

I've got a few minor hacks applied in various files to suit my project's needs, so whenever I upgrade, I have to go through and re-apply said hacks to the new version. Some of those hacks are to the "image.js" file in the plugins area. One of those hacks is to set a zero default for "txtBorder".

Another hack, though outside of CKE proper, is a JS script that runs on instanceReady, which parses through image tags, and takes various style values and creates standalone attributes, i.e. an img tag with "style-'width: 50px;'" will have "width='50'" added in as well.

(I do this because many of the pages that are edited by clients using CKE end up being used as HTML emails, and Outlook (yecch) chokes on styles in image tags, hence the need for the old-school attributes. I hate you Microsoft.)

One of the style types this script looks for is "border-width" and it extracts out just a plain "border" standalone attribute. The JS code looks for this value using a regex which looks for the presence of 'px'.

With 3.6, all was well - no matter the border value, zero or anything, when saved, the style was set to 'px'.

With 3.6.2, it seems that if the border is set to 0, the editor sets that value to be '0pt'. If it's anything else, 1, 2, 3, it sets it to be '1px', etc. Popping open the image popup and changing the border value around, to zero or a positive value, this behavior is consistent.

The demo of CKE on the product page behaves in the same fashion, so it's not anything I've done.

This is playing fob with my styles-to-attributes juggle process. And yes, I can fairly easily adjust my JS code to look for both 'pt' and 'px'. But this is an inconsistent behavior in CKE introduced with this new version, which is bothersome.