Properties option.
-
New user here. Finally decided to replace IE. It's getting a little long in the tooth and Edge isn't a suitable replacement for me (The UI is really really buggy, or nonexistant). Which is unfortunate. IE has been the best browser since 7 launched, IMO. A modern engine with IEs UI would be almost perfect.
Anyway, overall I'm liking this browser, but, something that bothers me about all browsers that's true here...
Where is the standard context menu on right click? Is there any way to restore it? It's one of the reasons I was still using IE. I use it all the time, and several of the options are just not in other browsers. Particularly the standard properties box, which I use multiple times a day. Why does no browser have this anymore? Surely I'm not the only user that used it...
With all the customizing here, why can I not just use the standard windows context menu?
-
@Sagelukahn Each browser has its own context menu. Is there really a standard for such a thing?
You can, however get the information seen in IE's Properties in Vivaldi by clicking the icon directly to the left of the URL and then clicking "Details."
-
There definitely is a standard windows context menu... all browsers used to use it. I have no idea why they stopped, stripped most of it out and called it a new feature. It's one of many reasons I never strayed from IE.
And that doesn't give me the windows property window, and would only do so for the page, how would one select an object and do that?
-
@Sagelukahn I'm looking at IE's menu right now. What windows property menu? There's Properties in the context menu, and that leads to the same info as you get via the badge in other browsers.
-
@rseiler : user is apparently talking about the "properties" selection at the bottom of the IE context menu that one gets with right-clicking an object. Same information we get if we right-click and select "inspect."
-
Inspect opens up the developer tools panel. It doesn't open up a windows object property panel. Like if you right clicked a folder in explorer and clicked properties, that sort of standard display of an objects properties. Also, IE has the inspect button as well which does the same thing as other browsers.
Maybe I really am one of the last ever people who use this daily... >_>
-
I'm curious, what are you getting out of object properties? There are 4 things, and surely Protocol (which you already know), Type (which is never available), and Address (which is easily known in other ways, like hovering) aren't it.
Is it whatever the first item is?
-
@Sagelukahn - When you open "inspect," you do not get the developer tools (tho it's a similar kind of data view). However, highlighted in the view that you just opened, is data concerning the object you right-clicked on. It's essentially the same data you get in your Properties dialogue, but without the fancy formatting. Just the data. The name of the object, its size, address, alt text, etc. Whatever PROPERTIES the object posseses.
-
There are 7 things, if you do it to an image.
The first item is the file or objects name.
Then there's protocol and type which as you say are pretty useless these days.
Then there is the address which is very useful and is not easily surmised by other means outside of pouring over page sources, hovering does not show you the location of the object, just where the object links to.
Then file size, which rarely shows up, but sometimes can be useful if it does.
Then dimensions, also very useful.
Then at the bottom you have the created and modified date for the file. Not especially useful, but can be sometimes.
-
@Ayespy No, it really does open the developer tools... Unless the window named "Developer Tools" isn't the developer tools.
Also, no, as far as I can tell the same information is not there. Though it's similar... But who knows? I can't read raw code. I'm not a programmer.
-
@Sagelukahn I see, I hadn't tried it on a pic.
-
@Gwen-Dragon ...It's been a standard windows function since, what, Win 3.0? All the other browsers used to have it. They all coded it out by not using the standard context menu. I remember when FF did so years ago, it was very deliberately removed. Yes, it's exclusive to IE these days, which baffles me, but it's a standard windows application thing.
I couldn't find an extension that restored this functionality (or anything else missing from the standard context menu). I am apparently one of very few who noticed it missing.
-
@Gwen-Dragon Why is that? I never understood why removing functionality was called a feature? They had to work harder to make it this way even, which is weird. They could've all just used windows built in functions for the whole lot.
-
@Gwen-Dragon Firefox definitely had it back in the day. They removed it years ago though.
-
@Gwen-Dragon There was a similar enough request. Upvoted. Guess I'll have to keep IE on my taskbar in the meantime.
-
@Sagelukahn Two things:
- There's no such thing as a "standard context menu". Each Windows program and app has it's own context menu and it can consist of various elements and commands - some being "standard" for the majority of other software (like e.g. "Cut", "Copy", "Paste" etc.) and some being specific for the app that their being used for (like eg. "Rotate Image" in Paint).
- It's true that some browsers have or had at some point the "Properties" command which would bring a window with properties of an element on which it was clicked, but the command and the properties box or window had to be built into the browser in order to offer such functionality in the first place.
-
@pafflick said in Properties option.:
@Sagelukahn Two things:
- There's no such thing as a "standard context menu". Each Windows program and app has it's own context menu and it can consist of various elements and commands - some being "standard" for the majority of other software (like e.g. "Cut", "Copy", "Paste" etc.) and some being specific for the app that their being used for (like eg. "Rotate Image" in Paint).
- It's true that some browsers have or had at some point the "Properties" command which would bring a window with properties of an element on which it was clicked, but the command and the properties box or window had to be built into the browser in order to offer such functionality in the first place.
- While there is a section of the available selections that differ based on what you right clicked on, the format and certain options are most definitely standard within windows. The properties button being an obvious one. Beyond that, the size, shape, and order of things is also a pretty standardized thing. It's so when you use different apps within windows you don't have to guess at what the context menu is going to look like per app, they are all the same, just the options might be slightly different.
Lots and lots of apps and even MS has been breaking this idea of a unified experience though, and it's one of the worst things about Windows 10. Edge, for example, really uses a completely non standard context menu (and there's almost no options in it).
- Maybe you're right that they had to build it themselves. It's been so long since I've seriously looked outside of IE for a main browser I can't remember what the properties box in FF did exactly.
But would it not be impossible to just open the file properties on it? That seems to be what IE does. I can't imagine it would require coding a whole new feature just to show that.
-
@Sagelukahn - Yes it will require coding a whole new feature. It, or something like it, will probably happen in time anyway.
-
@Sagelukahn said in Properties option.:
- While there is a section of the available selections that differ based on what you right clicked on, the format and certain options are most definitely standard within windows. The properties button being an obvious one.
They may look the same due to the use of the native Windows context menu and contain the same commands and options which work similarly across various programs and apps and therefore it may seem as if it was some kind of a standard set of options, but there's absolutely no such thing as a standard "properties" command. Each app has to build its own one and that obviously requires hours of coding.
Whereas simple context menu commands (like mentioned cut, copy, paste) may use standard system commands (cut, copy or paste) to execute such actions, there's no system command for "properties" in that field. Perhaps there's a way to call the File Explorer's native properties box, but that's again a handful of work for a programmer.
@Sagelukahn said in Properties option.:
Beyond that, the size, shape, and order of things is also a pretty standardized thing. It's so when you use different apps within windows you don't have to guess at what the context menu is going to look like per app, they are all the same, just the options might be slightly different.
That's because the app developer can choose whether to use the native system context menu (less work for programmer, less resource use on the client's end and the user may be already familiar with it) or whether to build their own (to have more features, provide same experience on different OS etc.).
@Sagelukahn said in Properties option.:
Lots and lots of apps and even MS has been breaking this idea of a unified experience though, and it's one of the worst things about Windows 10. Edge, for example, really uses a completely non standard context menu (and there's almost no options in it).
I wouldn't call anything "standard" here because each app can set its own standards. And you have to keep in mind that some users - those on the touch screen devices for example - may have the experience with Edge's context menu exactly the opposite to yours. I mean, something that you hate could be other's people's blessing while something they hate works perfectly for you.
@Sagelukahn said in Properties option.:
But would it not be impossible to just open the file properties on it? That seems to be what IE does. I can't imagine it would require coding a whole new feature just to show that.
But that's exactly what is required here - creating a whole new feature and ways of handling it. IE is a specific case since it was tied with the Windows File Explorer app for like forever and thus many things work or behave similarly on both, possibly leading to an illusion that there are some standard things in places where there are none... MS probably built the "properties" command for IE basing on the File Explorer's "properties" command and just left it there intact for many years - that's why it looks so ancient compared to current "properties" box in File Explorer...
-