repro: open Google Calender make a new appointment edit the appointment try to save the appointment result: nothing happens, the changes can't be saved works in Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1b1pre) Gecko/20080830031750 Minefield/3.1b1pre ID:20080830031750 Fails in the 20080831 and 20080901 nightlies regression from Bug 450733 ?
Status: UNCONFIRMED → NEW
Ever confirmed: true
(In reply to comment #1) > I don't think bug 450733 could have caused this. Is bug 407216 in the > regression range? Yes it was.
This works for me with Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.4; en-US; rv:1.9.1b1pre) Gecko/20080901020926 Minefield/3.1b1pre
Flags: wanted1.9.1? → blocking1.9.1?
with Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1b1pre) Gecko/20080831162801 Minefield/3.1b1pre ID:20080831162801 I get this message in the errorconsole when I open an appointment: Error: setting a property that has only a getter Source File: https://www.google.com/calendar/4cade4cbd057f03dfc722395f6f8591ccalendarjs_doozercompiled__nl.js Line: 2
BZ just backed out bug 407216, I'll get that build once it's out
after the partial backout https://bugzilla.mozilla.org/show_bug.cgi?id=407216#c108 the problem is gone.
10 years ago
Just to make sure, was there a "setting a property that has only a getter" JS error in this case? And if so, what were the file and line numbers?
Summary: Can't save an appointment in Google Calender → Can't save an appointment in Google Calendar
10 years ago
(In reply to comment #7) > Just to make sure, was there a "setting a property that has only a getter" JS > error in this case? And if so, what were the file and line numbers? Doesn't comment #4 cover your question ?
Er, yes. Sad with the obfuscated code, but certainly covers what I wanted to know.
is it ok to resolve this bug fixed now that it works again ?
Status: NEW → RESOLVED
Last Resolved: 10 years ago
No longer depends on: 453105
Resolution: --- → DUPLICATE
Duplicate of bug: 453105
You need to log in before you can comment on or make changes to this bug.