mapgie
@mapgie.co.uk
(She/her) Software Impostor. Collector of interests.
ADHD af. I regret most of the things I say.
🇪🇺🏳️🌈 #BLM
ADHD af. I regret most of the things I say.
🇪🇺🏳️🌈 #BLM
Most relatable conference talk silde ever, courtesy of @html5test.com at #HalfStack
November 12, 2025 at 10:19 PM
Most relatable conference talk silde ever, courtesy of @html5test.com at #HalfStack
November 4, 2025 at 1:04 AM
Whilst I'd like to blame the fragility and ineptitude of USB micro ports for this BlackBerry 8900 Curve not turning on, I have remembered what actually happened.
I tried to install the Yammer app on it circa 2010 (pre-Microsoft ownership) and it became instantly, permanently bricked. 🪦
I tried to install the Yammer app on it circa 2010 (pre-Microsoft ownership) and it became instantly, permanently bricked. 🪦
September 28, 2025 at 11:30 AM
Whilst I'd like to blame the fragility and ineptitude of USB micro ports for this BlackBerry 8900 Curve not turning on, I have remembered what actually happened.
I tried to install the Yammer app on it circa 2010 (pre-Microsoft ownership) and it became instantly, permanently bricked. 🪦
I tried to install the Yammer app on it circa 2010 (pre-Microsoft ownership) and it became instantly, permanently bricked. 🪦
Bought at Cash Converters for £20 in the late 2000s, this phone is "For Engineering Use Only" so
in retrospect, it's probably a stolen BlackBerry 8820.
Judging by the date, it thinks it's 2007. And I've no idea what the password might be.
in retrospect, it's probably a stolen BlackBerry 8820.
Judging by the date, it thinks it's 2007. And I've no idea what the password might be.
September 28, 2025 at 11:25 AM
Bought at Cash Converters for £20 in the late 2000s, this phone is "For Engineering Use Only" so
in retrospect, it's probably a stolen BlackBerry 8820.
Judging by the date, it thinks it's 2007. And I've no idea what the password might be.
in retrospect, it's probably a stolen BlackBerry 8820.
Judging by the date, it thinks it's 2007. And I've no idea what the password might be.
The back, for those who may be interested.
I should probably send them off to be recycled. I enjoyed taking the BlackBerry 8320 apart (not pictured), but there's probably not a lot I can do with the more modern phones.
I should probably send them off to be recycled. I enjoyed taking the BlackBerry 8320 apart (not pictured), but there's probably not a lot I can do with the more modern phones.
September 28, 2025 at 11:00 AM
The back, for those who may be interested.
I should probably send them off to be recycled. I enjoyed taking the BlackBerry 8320 apart (not pictured), but there's probably not a lot I can do with the more modern phones.
I should probably send them off to be recycled. I enjoyed taking the BlackBerry 8320 apart (not pictured), but there's probably not a lot I can do with the more modern phones.
I pulled out my history of mobile phones last night.
None of those using USB micro charging show signs of life. However, these older phones will turn on:
- USB mini-B charging (BlackBerry)
- Proprietary Samsung charger (SGH G600)
I still miss a good integrated hardware keyboard.
None of those using USB micro charging show signs of life. However, these older phones will turn on:
- USB mini-B charging (BlackBerry)
- Proprietary Samsung charger (SGH G600)
I still miss a good integrated hardware keyboard.
September 28, 2025 at 10:44 AM
I pulled out my history of mobile phones last night.
None of those using USB micro charging show signs of life. However, these older phones will turn on:
- USB mini-B charging (BlackBerry)
- Proprietary Samsung charger (SGH G600)
I still miss a good integrated hardware keyboard.
None of those using USB micro charging show signs of life. However, these older phones will turn on:
- USB mini-B charging (BlackBerry)
- Proprietary Samsung charger (SGH G600)
I still miss a good integrated hardware keyboard.
.scroll-text {
text-wrap: nowrap
font-size: 0.8rem;
min-width: fit-content;
}
text-wrap: nowrap
font-size: 0.8rem;
min-width: fit-content;
}
August 20, 2025 at 8:07 PM
.scroll-text {
text-wrap: nowrap
font-size: 0.8rem;
min-width: fit-content;
}
text-wrap: nowrap
font-size: 0.8rem;
min-width: fit-content;
}
If a Hotel website caps my password length at 15 characters and politely requests that I do not use special characters, should I just avoid them on principle?
August 18, 2025 at 8:22 PM
If a Hotel website caps my password length at 15 characters and politely requests that I do not use special characters, should I just avoid them on principle?
These were my most recent gateway back into it... Desperately lacking in range, and black keys.
And whilst I enjoy Garage Band on my 12" iPad, I too suffer from fat fingers. Plus, it loses something with the absence of the physical response to touch of the keys!
And whilst I enjoy Garage Band on my 12" iPad, I too suffer from fat fingers. Plus, it loses something with the absence of the physical response to touch of the keys!
August 9, 2025 at 10:27 PM
These were my most recent gateway back into it... Desperately lacking in range, and black keys.
And whilst I enjoy Garage Band on my 12" iPad, I too suffer from fat fingers. Plus, it loses something with the absence of the physical response to touch of the keys!
And whilst I enjoy Garage Band on my 12" iPad, I too suffer from fat fingers. Plus, it loses something with the absence of the physical response to touch of the keys!
I'm... I'm so sorry to have bothered you.
August 9, 2025 at 5:31 PM
I'm... I'm so sorry to have bothered you.
Build-time compiler errors for Blazor would make my life 12% better.
![Chrome dev console window reading:
Blazor.server.js:1
[2025-08-07T15:36:43.234Z] Error: System. InvalidOperationException: The type [redacted] declares a parameter matching the name 'EndpointDetails' that is not public. Parameters must be public. at Microsoft.AspNetCore.Components. Reflection.ComponentProperties.WritersForType..ctor (Type
targetType)](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:torygwypgwul7zk4gi4lfwty/bafkreic73z2ij7y56acyfqbrj3i6filpql3ytk3ywg3hw2ebhvmghkivjy@jpeg)
August 7, 2025 at 3:51 PM
Build-time compiler errors for Blazor would make my life 12% better.
I get my kicks where I get my kicks.
August 6, 2025 at 9:05 AM
I get my kicks where I get my kicks.
Anyone else get Push It stuck in their head from time to time?
August 4, 2025 at 5:00 PM
Anyone else get Push It stuck in their head from time to time?
My apologies to FluentUI for Blazor.
Part of my frustration at them is actually a fundamental frustration with the underlying HTML date input.
Behold, values using '/' are not appropriately parsed.
Values using "-" are parsed and displayed with "/".
🤡
Part of my frustration at them is actually a fundamental frustration with the underlying HTML date input.
Behold, values using '/' are not appropriately parsed.
Values using "-" are parsed and displayed with "/".
🤡
July 29, 2025 at 4:03 PM
My apologies to FluentUI for Blazor.
Part of my frustration at them is actually a fundamental frustration with the underlying HTML date input.
Behold, values using '/' are not appropriately parsed.
Values using "-" are parsed and displayed with "/".
🤡
Part of my frustration at them is actually a fundamental frustration with the underlying HTML date input.
Behold, values using '/' are not appropriately parsed.
Values using "-" are parsed and displayed with "/".
🤡
Far more usable on mobile, even if the layout is lacking.
Basic interactions like escaping out of the calendar and navigation by keyboard probably come under the "not fully compatible with accessibility" disclaimer.
I see no reason to use this over a standard html input at the moment.
Basic interactions like escaping out of the calendar and navigation by keyboard probably come under the "not fully compatible with accessibility" disclaimer.
I see no reason to use this over a standard html input at the moment.
July 28, 2025 at 8:43 PM
Far more usable on mobile, even if the layout is lacking.
Basic interactions like escaping out of the calendar and navigation by keyboard probably come under the "not fully compatible with accessibility" disclaimer.
I see no reason to use this over a standard html input at the moment.
Basic interactions like escaping out of the calendar and navigation by keyboard probably come under the "not fully compatible with accessibility" disclaimer.
I see no reason to use this over a standard html input at the moment.
DateTime pickers are beastly.
Temporality as a whole is a nightmare.
FluentUI for Blazor docs go further: when you type a / into the picker, naturally what you want is to enter a search command.
It displays as dd/mm/yyyy but certain cases expect dd-mm-yyyy input. Others expect nothing. Naturally.
Temporality as a whole is a nightmare.
FluentUI for Blazor docs go further: when you type a / into the picker, naturally what you want is to enter a search command.
It displays as dd/mm/yyyy but certain cases expect dd-mm-yyyy input. Others expect nothing. Naturally.
July 28, 2025 at 5:44 PM
DateTime pickers are beastly.
Temporality as a whole is a nightmare.
FluentUI for Blazor docs go further: when you type a / into the picker, naturally what you want is to enter a search command.
It displays as dd/mm/yyyy but certain cases expect dd-mm-yyyy input. Others expect nothing. Naturally.
Temporality as a whole is a nightmare.
FluentUI for Blazor docs go further: when you type a / into the picker, naturally what you want is to enter a search command.
It displays as dd/mm/yyyy but certain cases expect dd-mm-yyyy input. Others expect nothing. Naturally.
Thanks, that's helpful.
I'm going a bit mad trying to style my datagrids.
I'd greatly appreciate more direct control of width and element styling.
As an example, PropCols as buttons have a different styling to TemplateCols, including different font sizes, weights, and event typeface.
I'm going a bit mad trying to style my datagrids.
I'd greatly appreciate more direct control of width and element styling.
As an example, PropCols as buttons have a different styling to TemplateCols, including different font sizes, weights, and event typeface.
July 25, 2025 at 9:53 AM
Thanks, that's helpful.
I'm going a bit mad trying to style my datagrids.
I'd greatly appreciate more direct control of width and element styling.
As an example, PropCols as buttons have a different styling to TemplateCols, including different font sizes, weights, and event typeface.
I'm going a bit mad trying to style my datagrids.
I'd greatly appreciate more direct control of width and element styling.
As an example, PropCols as buttons have a different styling to TemplateCols, including different font sizes, weights, and event typeface.
Does everyone figure out their layouts by setting background-color to Squashies packet colours?
July 24, 2025 at 6:25 PM
Does everyone figure out their layouts by setting background-color to Squashies packet colours?
Yeah, fair.
I find troubleshooting excruciating amidst vague console errors, no step-into debugging, no compiler errors, and skeletal documentation. Can't put it all on FUIB!
While I've got you, I can't find info on the interactions of @ref, Data, and Items props on grids. Any guidance? Thank you.
I find troubleshooting excruciating amidst vague console errors, no step-into debugging, no compiler errors, and skeletal documentation. Can't put it all on FUIB!
While I've got you, I can't find info on the interactions of @ref, Data, and Items props on grids. Any guidance? Thank you.
![[2025-07-23T08:30:48.233Z] Error:
System. InvalidOperationException: Unable to evaluate index expressions of type 'PropertyExpression'
Microsoft.AspNetCore.Components. Forms. ExpressionFormatter. FormatIndexArgumen t(Expression indexExpression, ReverseStringBuilder& builder)
at
Microsoft.AspNetCore.Components.Forms.ExpressionFormatter. FormatIndexArgumen t(Expression indexExpression)
at Microsoft.AspNetCore.Components. Forms.FieldIdentifier. ParseAccessor [T]
(Expression'1 accessor, Object& model, String& fieldName)
at Microsoft.AspNetCore.Components. Forms.FieldIdentifier.Create [TField] (Expression'1 accessor)
Microsoft.FluentUI.AspNetCore.Components.FluentInputBase 1.SetParametersAsyn c(ParameterView parameters) in /_/src/Core/Components/Base/FluentInputBase.cs:line 317
at
Microsoft.AspNetCore.Components. Rendering.ComponentState. SupplyCombinedParam eters (ParameterView directAndCascadingParameters)](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:torygwypgwul7zk4gi4lfwty/bafkreia46gv3pjho2fyn6c7jzukdasendthdckdrycjp5zsrwbg2tbkeym@jpeg)
July 23, 2025 at 8:38 AM
Yeah, fair.
I find troubleshooting excruciating amidst vague console errors, no step-into debugging, no compiler errors, and skeletal documentation. Can't put it all on FUIB!
While I've got you, I can't find info on the interactions of @ref, Data, and Items props on grids. Any guidance? Thank you.
I find troubleshooting excruciating amidst vague console errors, no step-into debugging, no compiler errors, and skeletal documentation. Can't put it all on FUIB!
While I've got you, I can't find info on the interactions of @ref, Data, and Items props on grids. Any guidance? Thank you.
Here's an example, and the dev tools console is empty.
It might have something to do with binding to a dictionary but I'll have to look in the morning as I can't quite remember how I left it.
It might have something to do with binding to a dictionary but I'll have to look in the morning as I can't quite remember how I left it.
July 22, 2025 at 10:15 PM
Here's an example, and the dev tools console is empty.
It might have something to do with binding to a dictionary but I'll have to look in the morning as I can't quite remember how I left it.
It might have something to do with binding to a dictionary but I'll have to look in the morning as I can't quite remember how I left it.
"The current password may only contain letters and numbers."
Bit awkward because, well, it doesn't. 🙃
Bit awkward because, well, it doesn't. 🙃
![Change your login password
Field label: "Current password"
[text input box]
Error message: "The current password may only contain letters and numbers. "](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:torygwypgwul7zk4gi4lfwty/bafkreiep7fdnnvclus7qdkufpyum6d2h7lmpk7cxs4fbxribieggak7mg4@jpeg)
July 14, 2025 at 6:23 PM
"The current password may only contain letters and numbers."
Bit awkward because, well, it doesn't. 🙃
Bit awkward because, well, it doesn't. 🙃
"Anonymous function can be made 'static'"
"Can". But is there a reason it shouldn't be?
"Can". But is there a reason it shouldn't be?
July 11, 2025 at 9:07 AM
"Anonymous function can be made 'static'"
"Can". But is there a reason it shouldn't be?
"Can". But is there a reason it shouldn't be?