GenericMale

Thanks for looking into this, great questions. 1. Looks like this on mobile:  This can get quite long with a lot of engines enabled but it's collapsed by default,...

great idea to show the response time on the section header. just pushed this change. in case all the engines fail the collapsible is expanded by default anyway, so i...

makes no sense to show "Response time" on the label when everything failed 😅 it's the old text now in this case

@return42 Thank you for taking the time to look at this but it's honestly confusing to me why this was immediately rejected. There is an open feature request from january...

i just pushed a change (which i guess isn't shown here because the PR is closed) which addresses the internal object issue. it's now mapped the same as the UnresponsiveEngines....

Point 1 should hopefully be fixed in my branch. Point 2 is for sure up to discussion but I'm just confused why this wasn't already discussed as part of the...

> @GenericMale Based on return42's feedback, I propose we do the following. > > 1. Create a new branch from this one (`engine-timings-longest-only` or something) > > 2. Undo all...

> Almost good to be merged, I just have some minor notes before: > > * If there's a crashing engine, it's not properly aligned to the start of the...

> I still hesitate to merge this PR since I have a few doubts: > > Name collisions with other apps on the same domain are not solved (e.g. `language`...

@return42 maybe you can take a look again. basically everything should be configurable now and produce either an answer box, an infobox with or w/o image description or no answer/infobox...