TimJentzsch
TimJentzsch
> This makes working with sections less convenient and might trigger the bidi correction way too often (every time a text or style is changed - even if it is...
> > This makes working with sections less convenient and might trigger the bidi correction way too often (every time a text or style is changed - even if it...
In my opinion accessibility should be the default and not hidden behind options. Especially because it's harder to find those options if you already have visual impairments.
An easy temporary solution to improve the situation would be to set `loading="lazy"` for the images. Then they are only loaded when the user scrolls to the given card ([Docs](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/img#attr-loading)).
> - The icons seems to not be aligned with the centre of the tags > - The license icon is too close to the license tag > - If...
> The current layout adapts when there is no image. In my opinion that makes more sense than having a big gray box that is not used
I have a question regarding the run criteria example: ```rs .add_system(( tick_construction_timer, update_construction_progress) .chain() .run_if(construction_timer_finished) ) ``` Doesn't this mean "the timer is only ticked and the construction progress is...
> @TimJentzsch you're totally right. Good eye; I just pushed a fix for that. Nice! I think the comment is outdated now though: ```rs // This function can be used...
@alice-i-cecile Would it maybe work if we keep the separate timer update system, but change the app logic as follows? ```rs .add_system(update_construction_timer) .add_system( update_construction_progress .after(update_construction_timer) .run_if(construction_timer_finished) ) ``` I think...