Ticket #362 (new potential innovation)

Opened 4 years ago

Last modified 4 years ago

Turn context menu into a Firefox extension that integrates into the real menu

Reported by: clange Owned by: cdavid
Priority: minor Milestone: zzz Future zzz
Component: JOBAD Version:
Keywords: Cc: kohlhase, frabe
Blocked By: Blocking:
Due to close: YYYY/MM/DD Include in GanttChart: no
Dependencies: Due to assign: YYYY/MM/DD

Description

Advanced users of JOBAD in Firefox may consider the interference with the browser's context menu disturbing (#361). Therefore, we should offer a JOBAD variant for them, which does not have its own menu but integrates into the browser's one. This is possible with a firefox extension. However, it would require user to install that first.

Change History

  Changed 4 years ago by clange

  • owner changed from jgiceva to cdavid

follow-up: ↓ 3   Changed 4 years ago by cdavid

If we get the context menu right with Javascript, I'd rather stick with the Javascript, since this would be Browser Independent and Google Chrome does not support extensions.

Still, given the fact that the code depends on FF 3.5 and / or WebKit? derivatives, I wouldn't have anything against this.

An idea that came to me: maybe we should have another ticket, which should be dealt with very fast regarding the study whether we can drop the FF 3.5 requirement (backport to FF 3.0 or 3.1). Still, this is not a ... hot issue now.

in reply to: ↑ 2   Changed 4 years ago by clange

Replying to cdavid:

If we get the context menu right with Javascript, I'd rather stick with the Javascript, since this would be Browser Independent and Google Chrome does not support extensions.

I generally support this. It's just that this effectively disables the browser's context menu (#361), which might also be useful for getting certain things done. Regardless of how it's done, there should eventually be some way of keeping the browser's context menu accessible. The cheapest solution could be a way of temporarily disabling JOBAD's context menu.

An idea that came to me: maybe we should have another ticket, which should be dealt with very fast regarding the study whether we can drop the FF 3.5 requirement (backport to FF 3.0 or 3.1). Still, this is not a ... hot issue now.

I really wouldn't care about this. We are not developing business software but research prototypes. Looking at  some random web statistics, it should only be a matter of very few months until FF 3.0 is no longer being used widely. (3.1 is BTW the same as 3.5, they just renamed it.) And in those few months we have more important things to do.

Note: See TracTickets for help on using tickets.