Changes between Initial Version and Version 1 of Ticket #22406, comment 4
- Timestamp:
- Jul 30, 2020, 4:01:25 AM (4 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #22406, comment 4
initial v1 27 27 - disable certain security settings 28 28 29 It would be better if Django 1.11 could be patched to fix the issue .29 It would be better if Django 1.11 could be patched to fix the issue with the inconsistent handling of input for NullBooleanFields. 30 30 31 31 I don't know whether this same behaviour happens in Django 2.0 or above when using Chrome or Chromium, but it may be worth checking because just making a user click on intentionally wrong URLs in Chrome can result in a seemingly broken Django site.