You are a machine @rgb!
Thank you for these. I've checked every item against the current development build. You're right about most of them and have been added to the Feedback tracker. However, two could not be reproduced and I would appreciate a little more information on those.
Confirmed and tracked
Web page designer previews ignore font settings on several controls
RadioButtonGroup, TextArea, CheckBox, and TimePicker previews ignore the Typography properties (the same gap exists for a few other controls). The values are saved correctly and the running app honours them, so the preview is the defective side.
Web TimePickers and DateTimePickers ignore FontName and FontSize in Safari
I confirmed the font settings are delivered to the browser and they do apply in Chrome however the native time/date controls that Safari draws use a fixed system appearance and ignore font styling entirely. Whether to custom-draw the pickers so typography applies everywhere is part of the tracked issue. It would help to know which browser and OS you test with.
Non-interactive Web controls are tab stops with unthemed focus rings
Confirmed. These controls currently join the keyboard tab order even though they cannot be operated, and they then draw the browser's default blue outline instead of the app theme's focus ring. On desktop, non-interactive controls are not tab stops by default; the Web default should match.
Web Slider focus rings are drawn too small
Confirmed: the focus outline wraps an invisible 8-pixel element instead of the slider's visible 20-pixel extent.
Web ListBox HoverHighlight has no effect at runtime
The property is accepted and sent to the browser, but the client never uses it, so hovering rows never highlights them.
Suggestion: Default the application name to "WebApp"
Tracked as a feature request: Default new Web projects to the name WebApp
Add a context menu to the Web page designer surface
Right-clicking the page background does nothing; only controls have a context menu. The desktop window designer has one, so the Web page surface should match.
Not reproduced: More information needed
ListBox: "Set Text in ColumnWidths like 75% are cleared by Objo"
I could not reproduce this. Entering 75%,25% in the ColumnWidths field survives saving, reopening, and running, and the runtime computes the 75/25 split correctly - percentage widths and * widths are both supported. One related gap that can look like clearing: the designer preview always shows equal-width columns, so a width setting has no visible effect while editing.
To dig further, could you let me know:
- the exact text you entered and the ColumnCount at the time;
- where you saw the value "cleared" — in the inspector field after reopening the page, or when reading
ColumnWidths back in code at runtime?
- the Studio version, and a small sample project if possible.
Runtime : DatePicker and NumericField don't respect Enabled = false
Also not reproduced: in my tests a DatePicker or NumericField with Enabled = false (set in the designer or from code) is correctly disabled and dimmed, both at first display and when the property changes later.
Could you confirm:
- whether you set Enabled in the inspector or in code, and if in code, in which event;
- whether the control still accepts input, or whether it only fails to look disabled;
- your browser and OS.
Working as designed
Chart: "No Chart data." and the "View data" button
With no data, the empty-state message is intentional, and the "View data" button is the always-available accessible table view of the chart's data (it toggles to "Hide data"). If you would rather the button hid itself while there is nothing to show, that is reasonable feedback, say so and I'll take a look.
"You can't delete the only web page!"
A Web project must always have a default page, so the default page cannot be deleted until another default is chosen in Build Settings. Once a second page exists and is the default, the first page can be deleted normally. Perhaps this could be made more clear in the UI.
DatePicker popup opening outside the screen
The calendar popup is drawn and positioned by the browser itself (the native date input), so its placement is not under the application's control. It is noted alongside the picker work above in case the pickers move to a custom-drawn design, which would also give the popup consistent positioning.
Thanks again. Reports like this are exactly what the Web framework needs.