[Bug 41686] New: Strange unescaping of html-entities in itemcallnumber
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41686 Bug ID: 41686 Summary: Strange unescaping of html-entities in itemcallnumber Initiative type: --- Sponsorship --- status: Product: Koha Version: 25.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs@lists.koha-community.org Reporter: andreas.jonsson@kreablo.se QA Contact: testopia@bugs.koha-community.org CC: m.de.rooy@rijksmuseum.nl Go to a bibliographic record and edit an item. In itemcallnumber type: a & Save. The result is, as expected, that the itemcallnumber will be literally 'a &' Edit the item again and change to a & b Save. Now the itemcallnumber will be 'a & b' as if the string has been subject to an extra unescaping of html-entities. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41686 Phil Ringnalda <phil@chetcolibrary.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |phil@chetcolibrary.org --- Comment #1 from Phil Ringnalda <phil@chetcolibrary.org> --- Not just itemcallnumber, it happens for every item field you can type in, and also for bib records. You don't need the 'b', just '& ' - without the space it isn't unescaped. And without the semicolon it isn't unescaped, though & is one of the things where browsers don't require it. And '& ' isn't unescaped, despite that also being defined. Nor are '< ' or '> '. I didn't try the whole list of named character references from the spec, but if < isn't, there's no reason to think that ϶ would be. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
participants (1)
-
bugzilla-daemon＠bugs.koha-community.org