Buttons blank after updating to 1.6.3 (from 1.5.0)
See original GitHub issueDescribe the bug When running the following code in 1.5.0 you get a button with the text “Info” as expected. After updating to 1.6.3 it is blank (see screenshots).
Application.Init();
var w = new Window();
var btn = new Button
{
Text = "Info",
IsDefault = false,
};
w.Add(btn);
Application.Run(w);
Application.Shutdown();
Screenshots Running with 1.5.0
Running with 1.6.3
Desktop (please complete the following information):
- OS: Windows
- Terminal: Powershell
Issue Analytics
- State:
- Created a year ago
- Comments:16 (8 by maintainers)
Top Results From Across the Web
Add to cart button no longer working after update
Hi there, after an update of WC from 6.1.2 to 6.3.1 the add-to-cart buttons are no longer working. Update to WC 6.6.1 did...
Read more >Buttons gone - Frontend
After update to 2023.4.3 this morning all my buttons are a sort of “gone / empty”. Also the button card when trying to...
Read more >[SOLVED] LXDM boots to blank screen after NVIDIA ...
Hi,. After a "recent" system update including NVIDIA drivers to 410.73 415.18, I get a blank screen instead of my login / display...
Read more >Windows 11 Blank buttons? : r/WindowsHelp
I am noticing this in Windows Update as well with the 'Check for updates' button. When hovering, the 'Check for updates' text will...
Read more >With AngularJS : Bind a radio button input to a Boolean ...
Using AngularJS v1.5.0, I am trying to bind a radio input field to a Boolean variable that can be : true, false or...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
love all your work
@BDisp There’s a variant of that test incorporated in #1752 (lines 29 and 169 on in ButtonTests.cs) that catches the issue here if it recurs; I also added your Update_Parameterless_Only_On_Or_After_Initialize test which covers this. We’ve got good coverage of both the Text v TextFormatter desync and consistency between Text/TextFormatter and the resulting display contents with that PR now.