Using both nonWorkingTime and timeRanges causes crash

[lice@multinet.se]

It throws 'Cannot delete property 'timeRanges' of #<Scheduler>' during initialization

I was able to reproduce it by adding nonWorkingTime : true to your timeranges example, let me know if you need any more information to reproduce.

[johan.isaksson]

Hi,

I tried that on version 1.0.4 and it does not throw for me. Which version are you trying it on? Browser? Any other changes to the demo?

Best regards,
Johan Isaksson

[lice@multinet.se]

On version 1.04
Tried on Chrome,Firefox and Edge, it crashes on all of them for me.
On Firefox it throws 'property "timeRanges" is non-configurable and can't be deleted' rather than 'Cannot delete property 'timeRanges' of #<Scheduler>'

The only thing I changed was adding nonWorkingTime : true to features and it started crashing after a ctrl+f5

features: {
        stripe: true,
        timeRanges: {
            enableResizing: true,
            showCurrentTimeLine: true,
            showHeaderElements: true
        },
		nonWorkingTime : true
    }

/*original version
features: {
        stripe: true,
        timeRanges: {
            enableResizing: true,
            showCurrentTimeLine: true,
            showHeaderElements: true
        }
    }
*/

[johan.isaksson]

On the second attempt I was able to reproduce it. Not sure what I did wrong the first time but it throws as you described. Have created a ticket to track the bug here:

https://app.assembla.com/spaces/bryntum/tickets/6932

Thanks for your report!
//johan