|author||Michael Drake <firstname.lastname@example.org>||2019-11-30 15:38:21 +0000|
|committer||Michael Drake <email@example.com>||2019-11-30 15:38:21 +0000|
Dev weekend: Update my progress.
1 files changed, 9 insertions, 2 deletions
diff --git a/developer-weekend/dec-2019.mdwn b/developer-weekend/dec-2019.mdwn
index 8a6baf8..beb36d8 100644
@@ -88,9 +88,9 @@ Bug Triage
* [[!bug 2688]] - Assigned to Michael - Layout - Responded; needs CSS opacity support, which needs compositing.
* [[!bug 2694]] - Updated with notes, left acknowledged but unassigned
* [[!bug 2695]] - Resolved/Fixed thanks to Vince's new GTK UX
-* [[!bug 2689]] - Assigned to Michael - Layout
+* [[!bug 2689]] - Assigned to Michael - Layout - Fixed in HTML redraw
* [[!bug 2703]] - Daniel added a note, but we're leaving it unassigned
-* [[!bug 2710]] - This appears to be a RISC OS font problem, Michael to respond
+* [[!bug 2710]] - This appears to be a RISC OS font problem, Michael responded
@@ -101,6 +101,13 @@ Mostly individual activity here
+* [[!bug 2689]] - Fixed us not to render scrollbars when the CSS tells us
+ not to.
+* Added some extra glyphs to the Framebuffer front end to render the the
+ [wttr](https://wttr.in/) page properly.
+* [[!bug 2688]] - Looked into the cause of this bug, and found it was due
+ to the unimplemented opacity property. It's tricky to implement right
+ now. It applies to all descendant elements, so compositing is required.