Closed (won't fix)
Project:
Drupal core
Version:
7.x-dev
Component:
forms system
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
19 Dec 2007 at 16:29 UTC
Updated:
14 May 2015 at 21:56 UTC
Jump to comment: Most recent
Comments
Comment #1
gábor hojtsyI am not sure this is better. IMHO the normal font was used to provide a more readable sentence.
Comment #2
panchoDon't think that readability is a problem here. The sentences are short, and it is important that the user understands at first sight that the error message is referencing a specific field on this page: the field called E-mail address for example. We could also wrap the field name in single quotes, but that wouldn't be better. Think that this is the best solution indeed.
Comment #3
panchoComment #4
keith.smith commentedTo quote Gábor from http://lists.drupal.org/pipermail/development/2007-December/027977.html: "RC1 is string freeze, so whatever needs modifications in the strings is generally postponed to Drupal 7."
Comment #5
panchoWhow, this string freeze comes a bit early - there are still so many issues active...
Comment #6
panchoChanged back title
Comment #7
gábor hojtsyEarly? I hope the translators will not find it too late. Drupal 6 is a multilanguage release, so we'd like to see more translations getting ready by the release. Translators need time.
Comment #8
panchoGábor: Sure, I absolutely understand both the translators' needs and your urgent need to finally get this D6 release out! The point is, that I prefer the Debian style "Release is, whenever we're done." instead of setting fixed timeslots. But nevermind - if D6 were 100% perfect, there would be nothing to fix or improve anymore... :) Wish you Happy Christmas, and hope you can relax a bit after all tis work!
Comment #9
gábor hojtsyWell, nobody said that the RC1 will be on any specific day, so I don't see where do we set any fixed timeslot. With all the previous major releases, there was a string freeze timed right with RC1 and was pre-announced several times, just as it happened in this case. There is nothing new about this. Happy Holidays!
Comment #10
dries commentedI'm marking this won't fix. I don't think it is an improvement.
Comment #11
roball commentedBut why not using
instead of
? This would then allow to use custom CSS like
if you prefer emphasize field names (or styled in any way you like) in error messages, but would keep the format as it is if you don't set that CSS. Consider a field name Please select your favourite colors.. Currently, the user will be presented the following HTML error message:
which is hard to understand. If the field name would be wrapped into a class as suggested above, the message would be
instead, allowing it to be clearly understood.
Comment #12
roball commentedSince this won't be fixed in Drupal 7 core, I have written the Better Form Errors module which solves this problem. Re-assigning the previous status to this issue.