As you can see in the image attached, there is placeholder text for the URL parameters property, which is quite confusing because it matches that of default values for other properties, even though it’s actually not present. This should show as empty to no longer cause confusion.
(There is no tag for v2-1-3 yet but the version this is showing for me is 2.1.3.)
H Dustin,
Thanks so much for your report!
It serves as an example placeholder for the parameter format. I don’t know if it’s just me, but without that, I wouldn’t know how to use it.
Best regards,
timmse
The problem though is it is not consistent with other property types on elements, which is why it leads to confusion. Also URL query parameters are a very specific format, so I think anyone needing to use that property will know what to do, although regardless it should also be properly documented for anyone to learn how to use it without needing a placeholder text in the UI.
The main issue here is the inconsistency of this placeholder behaviour, as it looks the same as a default value assigned to other properties, so at a glance one can’t tell if this is a set default value or not.
The behaviour needs to be improved and align consistently with other properties.
Well, it would be completely pointless to set a default there… apart from the fact that it would also be visible in your address bar—which it isn’t, because it’s not a default.
Apart from that, I am not aware of any other reports on this issue, so it does not seem to be a problem for the majority of users—perhaps this will change in the future. However, it is still not a bug in the traditional sense 
Exactly, so why is this showing a value there then? That’s the point… that at a glance this appears to have a value even when it doesn’t actually have one, it’s very inconsistent to other properties and how they are set. If the idea is to illustrate to people how to use the property then you may as well do the same thing for other properties like padding, lol. There’s an inconsistency here and that’s the issue that needs to be fixed.
Whether it is reported by others or not doesn’t really matter here, it doesn’t negate the fact that there’s an inconsistency that must be fixed. What you wrote seems very dismissive of the issue which is sad to see.
If you don’t see this as a bug then kindly move this to the feature/improvements category, adding it to the list rather than dismissing it.
Thank you.
