... o coordinate testing. ユーザーインターフェースの変更は、必ず次の方法でテストしてください: Keyboard-only navigation. Common issues include: An interactive element can't be reached using the Tab or arrow keys. An interactive element "traps" input focus a ... ol with the Axe checker. Where the UI changes could affect those modalities, also test with: Touch-only navigation. Common issues include: A touch target (interactive element) is too small. Hover-based interaction that does not translate to touch, such ... as a hover-only tooltip. 400% browser zoom. Common issues include: Content is cut off or disappears when zoomed. Content that does not inherently require a two-dimensional layout c ... ... o coordinate testing. ユーザーインターフェースの変更は、必ず次の方法でテストしてください: Keyboard-only navigation. Common issues include: An interactive element can't be reached using the Tab or arrow keys. An interactive element "traps" input focus a ... ol with the Axe checker. Where the UI changes could affect those modalities, also test with: Touch-only navigation. Common issues include: A touch target (interactive element) is too small. Hover-based interaction that does not translate to touch, such ... as a hover-only tooltip. 400% browser zoom. Common issues include: Content is cut off or disappears when zoomed. Content that does not inherently require a two-dimensional layout c ... ... t use the ticket system to ask support questions. Use the Django Forum or the Django Discord server for that. Don't reopen issues that have been marked "wontfix" without finding consensus to do so on the Django Forum . Don't reopen issues that have bee ... isting benchmarks. どのように決定が下されるか ¶ Whenever possible, we aim for rough consensus. Emoji reactions are used on issues within the new feature ideas GitHub project to track community feedback. The following meanings are assigned to each react ... ion: ?: I support this feature and would use it ?: I oppose this feature or believe it would cause issues for me or Django ?: I have no strong opinion on this feature ?: This feature seems like a straightforward and beneficial a ... ... t use the ticket system to ask support questions. Use the Django Forum or the Django Discord server for that. Don't reopen issues that have been marked "wontfix" without finding consensus to do so on the Django Forum . Don't reopen issues that have bee ... isting benchmarks. どのように決定が下されるか ¶ Whenever possible, we aim for rough consensus. Emoji reactions are used on issues within the new feature ideas GitHub project to track community feedback. The following meanings are assigned to each react ... ion: ?: I support this feature and would use it ?: I oppose this feature or believe it would cause issues for me or Django ?: I have no strong opinion on this feature ?: This feature seems like a straightforward and beneficial a ... ... security issues in Django 1.3. Django 1.3.1 is a recommended upgrade for all users of Django 1.3. For a full list of issues addressed in t ... sory . 前のトピックへ Django 1.3.2 リリースノート 次のトピックへ Django 1.3 リリースノート 関連キーワード security release issues リリースノート September first series fixing several recommended upgrade users list addressed advisory クイック検索 Last u ... ... .3. Django 1.3.2 is a recommended upgrade for all users of Django 1.3. For a full list of issues addressed in this release, see the security advisory . 前のトピックへ Django 1.3.3 リリースノート 次のトピックへ Django 1. ... 3.1 リリースノート 関連キーワード security release issues リリースノート July second series fixing several recommended upgrade users list addressed advisory クイック検索 Last updat ... ... 4. Django 1.4.1 is a recommended upgrade for all users of Django 1.4. For a full list of issues addressed in this release, see the security advisory . 前のトピックへ Django 1.4.2 リリースノート 次のトピックへ Django 1. ... 4 リリースノート 関連キーワード security release issues リリースノート July first series fixing several recommended upgrade users list addressed advisory クイック検索 Last update ... ... several security issues present in Django 1.2.5. Django 1.2.6 is a recommended upgrade for all users of any Django release in the 1.2.X series. Fo ... r a full list of issues addressed in this release, see the security advisory . 前のトピックへ Django 1.2.7 リリースノート 次のトピックへ Django 1. ... 2.5 リリースノート 関連キーワード security release series issues リリースノート September sixth bugfix fixing several present recommended upgrade users list addressed advisory クイック検索 ... ... se corrects the following problems: The patch applied for the security issue covered in Django 1.2.2 caused issues with non-ASCII responses using CSRF tokens. The patch also caused issues with some forms, most notably the user-editing fo ... ピックへ Django 1.2.4 リリースノート 次のトピックへ Django 1.2.2 リリースノート 関連キーワード release problems patch caused issues forms リリースノート fixed couple released days after corrects following applied security issue covered responses using to ... ... .3. Django 1.3.2 is a recommended upgrade for all users of Django 1.3. For a full list of issues addressed in this release, see the security advisory . 前のトピックへ Django 1.3.3 リリースノート 次のトピックへ Django 1. ... 3.1 リリースノート 関連キーワード Django security release issues リリースノート July second series fixing several recommended upgrade users list addressed see advisory 関連するページ Djan ... 2026年10月08日