Langkau ke kandungan utama
Tiada item ditemukan.
logo dropboxsign
Mengapa Dropbox Sign?
Kembangkan atau runtuhkan akordion

Apa yang boleh anda lakukan

Tandatangan Dokumen Dalam Talian
Cipta tandatangan elektronik
Pilih atau cipta templat
Isi dan tandatangan PDF
Lengkapkan kontrak dalam talian
Pengurusan Dokumen
Terokai ciri
ikon anak panah ke kanan

Kes Gunaan

Jualan dan pembangunan perniagaan
Sumber manusia
Syarikat baru
Teknologi kewangan
Harta Tanah
Perkhidmatan Atas Permintaan
Produk
Kembangkan atau runtuhkan akordion
ikon dropbox
Sign
Permudahkan penghantaran dan tandatangan
ikon dropbox
Tandatangan API
Sepadukan e-Tandatangan dalam aliran kerja anda
ikon dropbox fax
Fax
Hantar faks tanpa mesin faks.
ikon integrasi dropbox
Integrasi
Kami tersedia di tempat anda bekerja
Sumber
Kembangkan atau runtuhkan akordion
Blog
Kepakaran aliran kerja & berita produk
Kisah pelanggan
Kisah dunia sebenar dengan hasil sebenar
Pusat bantuan
Panduan mendalam untuk produk kami
Pustaka sumber
Laporan, video dan helaian maklumat
Pembangun
Harga
Kembangkan atau runtuhkan akordion
Harga Dropbox Sign
Dapatkan pelan yang sesuai untuk anda
Harga API Dropbox Sign
Kisah dunia sebenar dengan hasil sebenar
Hubungi jualan
Daftar
Hubungi Jualan
Daftar masuk
Kembangkan atau runtuhkan akordion
Dropbox Sign
Dropbox Forms
Dropbox Fax
Percubaan percuma
Blog
/
Pembangun

Getting React and Webpack to Run on IE8 (If You Must)

by 
Freddy Rangel
June 9, 2016
3
minit bacaan
Getting React and Webpack to Run on IE8
ikon petua alat

Produk hebat yang sama dengan wajah baru! HelloSign kini dikenali sebagai Dropbox Sign.

ikon tutup

This post was originally published by Freddy Rangel on Medium.

‍

–––

‍

You might ask yourself, “why in the world would anyone want to torture themselves by supporting IE8?” Even Google doesn’t support IE8! But there are actually many companies that must support IE8 for one reason or another. At the company where I work, Dropbox Sign, we allow third-party companies to embed our document signing software directly in their applications. Many of our customers support IE8. Therefore, we must support IE8 as well.

‍

Recently, we received a report that IE8 users could not sign documents on our site. We take these kinds of bugs very seriously. Signing agreements is no trivial matter: they’re the written documents that outline the relationships and obligations of our lives. If our users can’t sign documents, they can’t do the basic tasks to get things done. A bug like this can have a huge impact on individuals and businesses alike.

‍

The cause of this bug for IE8 users was our rewrite of many parts of our application using React and Webpack. As it turns out, there are quite a few changes needed in order to get these two libraries to run on IE8. Here’s how we did it.

‍

ES5 Polyfill

‍

React and Webpack support ES5 and above. IE8, however, runs ES3, so you’ll need a polyfill to be able to run ES5 code. You can find the ES5 shim here: ES5 Shim.

‍

Set NODE_ENV to Production

‍

This change not only makes your React application much faster, but also removes a lot of code in development that are not supported on IE8. There’s a little more to it that just setting your NODE_ENV, but luckily I already wrote a blog post about how to do that and more: How to Make Your React Apps 10x Faster.

‍

ES3ify Your Code

‍

Even with a polyfill, there is much ES5 code that will break on IE8. One prominent example is the reserved words in IE8, words used as key names in an object. `class`, `catch`, and `default` are reserved works in ES3. ES3ify will change your code to avoid these conflicts with ES3

‍

‍

.

‍

Babel Transforms

‍

For good measure, I recommend using 2 Babel transforms that do much the same thing as ES3ify: Transform-es3-property-literals and transform-es3-member-expression-literals. We have a lot of legacy code that we’re not running through Babel, so we need to use ES3ify. We also use the Babel transforms just to be on the safe side.

‍

Watch Out for IE8 Gotchas

‍

One interesting gotcha I discovered was the incompatibility of the getter syntax in IE8. Many developers assume getters are an ES2015 feature, but they are actually ES5. This means that if you’re using getters in ES2015 classes, Babel will simply use the ES5 getter syntax. Unfortunately, this blows up on IE8. 

‍

There is support for getters in IE8, however, it is only compatible with DOM nodes. My suggestion: Avoid getters if you must support IE8.

Kekalkan penglibatan

Siap! Sila periksa peti masuk anda.

Thank you!
Thank you for subscribing!

Lorem ipsum

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique. Duis cursus, mi quis viverra ornare, eros dolor interdum nulla, ut commodo diam libero vitae erat. Aenean faucibus nibh et justo cursus id rutrum lorem imperdiet. Nunc ut sem vitae risus tristique posuere.

Lorem ipsum
ikon anak panah ke kanan
ikon tutup

Up next:

Ilustrasi dekat tandatangan tulisan tangan, mewakili penyelesaian tandatangan digital moden.
Pembangun
15
minit bacaan

Mengintegrasikan Dropbox Sign dengan Ruby on Rails: Tutorial Langkah demi Langkah

Ilustrasi dekat tandatangan tulisan tangan, mewakili penyelesaian tandatangan digital moden.
Pembangun
15
minit bacaan

Dropbox Sign vs. SignNow for developers

Video

Sediakan tandatangan terbenam dalam Java menggunakan Dropbox Sign

Produk
Dropbox SignDropbox Sign APIDropbox FaxIntegrasi
Sebab Dropbox Sign
Tandatangan elektronikTandatangan dokumenTandatangan dan Isi PDFKontrak dalam talianCipta tandatangan elektronikEditor TandatanganTandatangan Dokumen Word
Sokongan
Pusat bantuanHubungi jualanHubungi sokonganUrus kukiBermula: Dropbox SignBermula: Dropbox Sign API
Sumber
BlogKisah pelangganPusat sumberPanduan KesahihanPusat amanah
Rakan niaga
Rakan Niaga StrategikPencari rakan niaga
Syarikat
KerjayaTermaPrivasi
ikon facebookikon youtube

Kaedah pembayaran yang diterima

Logo MastercardLogo VisaLogo American ExpressLogo Discover
Lencana Pematuhan CPALencana pematuhan HIPAALencana Sky High Enterprise ReadyLencana Diperakui ISO 9001

Tandatangan elektronik Dropbox Sign adalah sah di sisi undang-undang di Amerika Syarikat, Kesatuan Eropah, United Kingdom, dan banyak lagi negara di seluruh dunia.
Untuk mendapatkan maklumat lanjut, sila lihat Terma dan Syarat serta Dasar Privasi kami