Bugzilla

We should decide this before the auto-formatting of JS code happens (in bug 1572047).  If all goes well, I'd like to land that bug right before the next TB beta release (the one corresponding to FF 70, which is released on Tues Sept. 3rd).  That will make it easy to backport changes to the beta release.  That's roughly three weeks from now.  This change answers the automation question(s).

As someone who works on both TB and Calendar code, I'd be in favor of standardizing on 2 space indent for both.  Among other things it makes the limited number of characters per line go further.  I'm accustomed to 2 space indent and I've found the readability is fine for me.

We should decide this before the auto-formatting of JS code happens (in bug 1572047).  If all goes well, I'd like to land that bug right before the next TB beta release (the one corresponding to FF 70, which is released on Tues Sept. 3rd).  That will make it easy to backport changes to the beta release.  That's roughly three weeks from now.  This answers the automation question(s).

As someone who works on both TB and Calendar code, I'd be in favor of standardizing on 2 space indent for both.  Among other things it makes the limited number of characters per line go further.  I'm accustomed to 2 space indent and I've found the readability is fine for me.

We should decide this before the auto-formatting of JS code happens (in bug 1572047).  If all goes well, I'd like to land that bug right before the next TB beta release (the one corresponding to FF 70, which is released on Tues Sept. 3rd).  That will make it easy to backport changes to the beta release.  That's roughly three weeks from now.  

The changes in that bug answer the automation question(s).

As someone who works on both TB and Calendar code, I'd be in favor of standardizing on 2 space indent for both.  Among other things it makes the limited number of characters per line go further.  I'm accustomed to 2 space indent and I've found the readability is fine for me.