Closed Bug 1265774 Opened 6 years ago Closed 6 years ago

EditComments doesn't work in 5.0.2

Categories

(bugzilla.mozilla.org :: Extensions, defect)

Production
defect
Not set
normal

Tracking

()

VERIFIED WONTFIX

People

(Reporter: altlist, Unassigned)

References

()

Details

I have been using a 12-2014 snapshot of EditComments that worked fine in 5.0rc3 as well as 5.0.2.  But the latest snapshot of EditComments doesn't work in 5.0.2.

I have not dug deeper to figure out why.
the editcomments extension was reworked in bug 1153101, and now only supports BMO's new show_bug UI (ie. it won't work on upstream bugzilla anymore).

the last revision that may work is https://github.com/mozilla/webtools-bmo-bugzilla/tree/5265c09db899e148ceef6ba47aa199fa1e282e7b/extensions/EditComments
Thanks Byron, any plans to make EditComments aligned with Bugzilla?  Or perhaps after bug_modal have been migrated to Bugzilla?
(In reply to Albert Ting from comment #2)
> Thanks Byron, any plans to make EditComments aligned with Bugzilla?  Or
> perhaps after bug_modal have been migrated to Bugzilla?

Not from the BMO team specifically. When/if bug modal is merged upstream, it should make it easier to make the extension part of the core by someone who wants to take on the task.

dkl
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
A working version of EditComments is now at https://github.com/bugzilla/EditComments and patches are welcome.

There is even a branch (modal) for the same version we have in bmo, which we may need since Modal is going to be ported for Bugzilla 6.
Status: RESOLVED → VERIFIED
Thanks.  Hopefully this will eventually be moved to bugzilla itself, as well as InlineHistory.  They both work quite well.
EditComments is far more likely to be upstreamed in its current form. InlineHistory is a mess to integrate.
I've been using InlineHistory for about a year as well.  No major issues other than some Markdown integration updates such as bug 1130760
Component: Extensions: EditComments → Extensions
You need to log in before you can comment on or make changes to this bug.