Ken Howard

I'm doing something outside of FitText that may be helpful to someone... ``` $('.fittext, .fit-text, h1 span, h2 span, h3 span, h4 span, h5 span, h6 span').each(function() { $(this).fitText($(this).data('compress')); });...

The reason we use parseInt is because a percentage is not a valid value for the width property.

A percent unit on height does nothing (It has no value to base itself upon). Width of a percentage unit does indeed expand to a percentage of it's container, although...

@kkirsche By the property being "ignored", I don't think it should be "removed". In the details they do intend on using the version property in the future. That's my take...

@jcdarwin @davatron5000 Here's the convo around why we added the check: https://github.com/davatron5000/FitVids.js/commit/8054992d321678c4b62abfc5b305c8b422194a35

@jcdarwin I'm ok with this latest change. Detecting that the style attribute has both a height and width is better than detecting if the element has a style and width...

@Diazbesjorge If you could provide a reduced test case for this I'd be glad to look at the issue. FitVids isn't watching the DOM for new elements so you should...

Hey Joe. There are no plans to add any new video vendors to the current list as we have a way to do this with the [customSelector option](https://github.com/davatron5000/FitVids.js#add-your-own-video-vendor).

Awwe Snap! I should be following the hot drama of @davatron5000 then. Sorry guys. Putting this on the roadmap for something new and amazing.

I think this is somewhat related to #50 where a user could get prompted for a filename if one doesn't exist. However, the current extension will only update files in...