Re: [Apache Bloodhound] #291: Impossible to reply some comments in i.a.o after #290
#291: Impossible to reply some comments in i.a.o after #290 -+- Reporter: olemis | Owner: nobody Type: defect | Status: closed Priority: critical| Milestone: Release 4 Component: ui design |Version: Resolution: worksforme | Keywords: ticket comments -+- Changes (by gjm): * status: new = closed * resolution: = worksforme Comment: Apart from any association with the problem fixed in #289, I don't see a specific problem. The only places where items in the change history cannot be edited that I have noted are where the item is an attachment event which is, for some reason, not treated as a comment event. Perhaps it is worth considering enhancements to this so that it is not confusing but unless there are cases that I have missed, there appears to be nothing to fix. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/291#comment:2 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #291: Impossible to reply some comments in i.a.o after #290
#291: Impossible to reply some comments in i.a.o after #290 -+- Reporter: olemis | Owner: nobody Type: defect | Status: closed Priority: critical| Milestone: Release 4 Component: ui design |Version: Resolution: worksforme | Keywords: ticket comments -+- Comment (by olemis): Replying to [comment:2 gjm]: Apart from any association with the problem fixed in #289, I don't see a specific problem. yes, it seems that this issue was related to the initial (buggy) solution to correct anchor position due to the fact that overlapping elements prevented comment DOM elements to trigger hover events. The only places where items in the change history cannot be edited that I have noted are where the item is an attachment event which is, for some reason, not treated as a comment event. yes that's correct . Perhaps it is worth considering enhancements to this so that it is not confusing but unless there are cases that I have missed, there appears to be nothing to fix. Yes . it's ok to close this ticket since it's yet another side-effect of the problem fixed in #289 . -- Ticket URL: https://issues.apache.org/bloodhound/ticket/291#comment:3 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #291: Impossible to reply some comments in i.a.o after #290
#291: Impossible to reply some comments in i.a.o after #290 +- Reporter: olemis | Owner: nobody Type: defect | Status: new Priority: critical | Milestone: Release 4 Component: ui design |Version: Resolution: | Keywords: ticket comments +- Changes (by olemis): * cc: olemis+bh@… (added) * priority: major = critical * keywords: = ticket comments * milestone: = Release 4 Old description: New description: After #290 Reply and Edit buttons in ticket comments are hidden by default and shown on hovering comment div . Nonetheless , for some reason I can't figure out yet , sometimes they are not shown on hover . -- Comment: Maybe this ticket is related to #289 and #292 . Since situation is looking weird at the moment I'll continue with this one once the other two will be closed . -- Ticket URL: https://issues.apache.org/bloodhound/ticket/291#comment:1 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
[Apache Bloodhound] #291: Impossible to reply some comments in i.a.o after #290
#291: Impossible to reply some comments in i.a.o after #290 ---+ Reporter: olemis | Owner: nobody Type: defect | Status: new Priority: major | Component: ui design Version: | Resolution: ---+ -- Ticket URL: https://issues.apache.org/bloodhound/ticket/291 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
