Actions
Bug #3714
closed[Workbench] small bugs in "report bug on the page" feature
Status:
Resolved
Priority:
Normal
Assigned To:
Radhika Chippada
Category:
-
Target version:
Start date:
08/27/2014
Due date:
% Done:
100%
Estimated time:
(Total: 3.00 h)
Story points:
0.5
Updated by Ward Vandewege over 10 years ago
- Target version set to Arvados Future Sprints
Updated by Ward Vandewege over 10 years ago
- Target version changed from Arvados Future Sprints to 2014-09-17 sprint
Updated by Ward Vandewege over 10 years ago
- Subject changed from small bugs in "report bug on the page" feature to [Workbench] small bugs in "report bug on the page" feature
Updated by Radhika Chippada over 10 years ago
- Assigned To set to Radhika Chippada
Updated by Radhika Chippada over 10 years ago
- Status changed from New to In Progress
Updated by Brett Smith over 10 years ago
Reviewing 0313947
- It feels a little unfortunate that the disable code is duplicated, once in the JavaScript's main body and a second time in the input change event. Would it be possible to define a function, call it immediately, and then bind it to the event?
- I'm not sure I understand the purpose of the
trigger
boolean. Would it be simpler to just write the desired actions directly inif
andelse
clauses? - My understanding is that it's JavaScript best practice to use the
===
operator instead of==
for most comparisons against specific values. This page illustrates the issues with==
. - In
report_issue_test.rb
, the button assertion before sending the report is not indented consistently.
Thanks.
Updated by Radhika Chippada over 10 years ago
- Status changed from In Progress to Resolved
Applied in changeset arvados|commit:21c6d252b279c9714419bf65da07e32246572238.
Actions