- From: Aleksandar Totic via GitHub <sysbot+gh@w3.org>
- Date: Fri, 02 Apr 2021 23:01:21 +0000
- To: public-css-archive@w3.org
> Is it so bad to just simply print a verbose warning to the console like Chrome does today and call it a day? Console warnings are outside of the spec. The error warning was explicitly designed to get developer's attention. The theory behind it was that without the error, it would be easy to develop badly performing code. We've had some hallway conversations about this. The core of the problem might be: - sometimes RO limit error is acceptable, and there is no way for web developers to distinguish between acceptable and unacceptable errors inside the error handling routine. What can we do about it? Some options are: 1) Provide "suppressNextROError" function inside their RO callback which suppresses next error. Pros: easy for developers to do. Cons: easy to just always call it, and completely ignore this error. 2) Provide "annotateNextError(msg)" function inside RO callback which would add msg to the error string. Developers could use this to filter out errors in the error reporting routine. -- GitHub Notification of comment by atotic Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6173#issuecomment-812747494 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 2 April 2021 23:01:23 UTC