Activity log for bug #1752367

Date Who What changed Old value New value Message
2018-02-28 16:29:34 Jason Boyer bug added bug
2018-04-23 15:14:53 Kathy Lussier evergreen: status New Confirmed
2018-04-23 15:14:55 Kathy Lussier evergreen: importance Undecided Medium
2018-04-23 15:15:08 Kathy Lussier tags webstaffclient
2018-10-31 16:45:44 Elizabeth Thomsen bug added subscriber Elizabeth Thomsen
2018-12-13 17:47:46 Joan Kranich bug added subscriber Joan Kranich
2019-03-07 17:48:03 Tiffany Little tags webstaffclient cataloging webstaffclient
2019-04-04 15:56:12 Jo-Anne Teeuwsen bug added subscriber Jo-Anne Teeuwsen
2019-06-20 14:15:18 Lindsay Stratton bug added subscriber Lindsay Stratton
2020-01-15 19:03:45 Anna Goben tags cataloging webstaffclient cataloging patron statcats webstaffclient
2020-01-31 15:54:36 Beth Willis bug added subscriber Beth Willis
2021-02-12 01:51:20 Jennifer Pringle summary Can't Edit Stat Cat Entries in Web Client Can't Edit and Delete Stat Cat Entries in Web Client
2021-02-12 01:52:22 Jennifer Pringle bug added subscriber Jennifer Pringle
2021-02-12 21:50:03 Kyle Huckins bug added subscriber Kyle Huckins
2021-02-12 21:56:04 Mike Risher bug added subscriber Mike Risher
2021-02-16 16:54:48 Christine Morgan bug added subscriber Christine Morgan
2021-03-16 19:47:43 Timothy Means tags cataloging patron statcats webstaffclient cataloging patron statcats
2024-01-02 19:16:01 Terran McCanna tags cataloging patron statcats cataloging needsdiscussion patron statcats
2024-11-12 19:16:09 Michele Morgan description Because of the way that different browsers trigger (or don't) onclick handlers for option tags, there's no way to trigger an edit on existing stat cat entries in most browsers. Because of its lineage, Firefox is still able to edit them since it works in the same way as the XUL client. I realize this interface will be completely rewritten when it's Angular-ized, but I wanted to make sure this quirk was documented in case it has an effect on how it's written. i.e. this was done so you can edit an entry even if an onchange handler wouldn't be triggered; I don't know if Angular gets around that some other way or if it should just be changed to a mode with a button to click. (Probably, for discoverability...) Updating this description since the patron and item statistical category editors have been ported to Angular as separate interfaces as of 3.12. With this port (bug 1857911), editing and deleting statistical category entries was intentionally disabled pending further discussion, which has begun here.