It is now 2017 and we are once again asking ourselves if it is now time to drop support for IE8 in JPDF2HTML5?
The answer to this question for us lies with our customers – do they need support for IE8?
So, if you still require support for IE8, please let us know!
What would it mean for the product?
We would remove the following Text Modes:
- – svg_realtext_with_ie8fallback
- – svg_shapetext_nonselectable_with_ie8fallback
- – image_realtext_with_ie8fallback
- – image_shapetext_nonselectable_with_ie8fallback
We would remove EOT from the list of available font types we generate.
What would it mean for us?
We would be able to remove a lot of complexity from the code base that deals exclusively with supporting IE8. This would make it easier and faster to work on JPDF2HTML5 to make improvements and add to new features.
What would it mean for you?
You would benefit from simpler output and our ability to iterate faster.
Of the users that visit our websites, less than 0.1% are still using IE8. We think it’s now time.
Subject to your feedback, our plan is to deprecate our IE8 support in the next release and then to remove the features later in the year.
Latest posts by Leon Atherton (see all)
- Making a Simple Basecamp Chatbot with NodeJS - November 29, 2017
- My Business of Software Conference Experience – BoS Europe 2017 - June 7, 2017
- Do you still need IE8 support in JPDF2HTML5? - February 8, 2017
- JPDF2HTML5 2016 Roundup and looking ahead to 2017 - December 20, 2016
- What Chrome 45 dropping NPAPI Plug-in support means - September 10, 2015