> A: It's cooled through our large heatsink and ultra quiet Noctua fan. The fan only turns on above 75% brightness. At max power, the heatsink is cool enough to put your hands on it for a couple of seconds.
CENELEC Guide 29, referenced in EU harmonized standards sets burn thresholds:
For brief contact (e.g., 1-3 seconds on adult-accessible parts), temperatures should stay below ~48-55°C depending on material; longer reflexive contact requires even lower limits (e.g., 43°C for extended exposure). A surface hot enough that hands can only tolerate it for "a couple of seconds" implies it's above this (likely 60°C+), risking second-degree burns.
I practice this means this product would not be allowed to be sold in EU. This would have been thoroughly tested to get the CE mark.
> All LED lights sold in Europe must carry the CE mark
Well, at no point do they talk about any kind of certification so my guess is they just didn't care/know/worry about it. So, yes, it's probably not legal to sell this in many places -not just EU-.
Thanks. When I tried to use the https://www.githubstatus.com/ link it wouldn't let me submit. Now I will remember to use the incident link in the future. I hadn't noticed that before.
1. Without touching the default colours: If I select a title to edit it, it appears as "very light grey on light blue background" which is extremely hard to read. The very light grey is not ideal on white background anyway, so maybe it would be better to use another default colour for titles.
2. What email clients has the resulting HTML been tested on?
3. There are some problems with the "primary button" block. First there doesn't seem to be any way to change the button's colour. It's blue and there's no way to change that. The block that contains it has a white background which can be changed, but not the background of the button itself. Then there's the text colour -which by default is another poor option, green text on blue background- which you can try to change but when you press "apply changes" it has no effect, and when you click the element again the property goes back to showing green as the colour. The same happens with the "outline button".
4. In a "Text Content" -"paragraph with heading and text"- there are also some colour problems. The properties only show the text colour of the heading but not that of the text paragraph. But then if I do select a colour and apply changes, it only changes the colour of the text paragraph but there seems to be no way to change the text colour for the heading. The same applies to the "basic header", where you can change the colour of the sub-heading but not that of the larger heading text.
5. I can't select some text with the mouse when editing it. If I try, it tries to move the block. I can select a bunch of text if I use the keyboard -e.g. ctrl+shift+arrow- but it's hard to justify that I can't do it with the mouse in a so-called visual environment.
6. A "text content" block contains exactly 1 heading and 2 paragraphs. The second of those paragraphs says "Add more paragraphs as needed..." but there doesn't seem to be any way to do that and add any additional paragraphs to the block. For that matter, there also doesn't seem to be any way to remove a paragraph from the block.
I'm sorry to be so blunt but this seems almost useless.
I just tried something like...
let someArray = [
"one",
"two",
"three"
];
...and it warns that it's missing semicolons on all those lines -except for the last one, obviously-. And the fix is...
Your code:
let someArray = [
Fix:
let someArray = [;
But then I tried something with an actual syntax error.
It says...
Syntax Error
Line 1
ERROR
JavaScript cannot read this line because something is typed wrong.
...which doesn't seem very helpful, not even pointing where in the line the error lies (which acorn does tell you). So I open the dropdown to see the explanation and fixes. The explanation is...
The code breaks basic JavaScript rules.
...and the suggested fixes are...
Fix the typo. Look for missing or extra symbols like ), }, ], or ;.
So I wonder, what does this actually say beyond the original "syntax error"? How is it helpful at all?
Also, looking at the code I find all sort of failing rules which just don't work.
"Assignment in condition":
This will show a warning, while being perfectly fine:
if (flag) a = null;
This will not show a warning at all:
if (a = 2) b = 3;
Then there's the rules for unused variables and for undeclared variables. Those simply do not work at all. They never find anything. It looks like you're expecting acorn to modify your code so that you can later go through it line by line but it just doesn't work that way.
https://imgur.com/a/WdLWpfq
reply