Having blazed a trail with email in Hotmail and later Outlook Web Access, in 2010 Microsoft launched the first version of the Office web applications, meaning you could run lightweight Word, Excel and PowerPoint in your browser, as a companion or even as an alternative to the full-fat desktop versions. A few years earlier, Google Docs released as an online word processor (and later, other types of productivity apps, rebranding as G Suite and now Google Workspace). There are pros and cons of the browser-only experience; you tend to sacrifice some functionality compared to the desktop applications in favour of ubiquitous availability, though web clients can be updated more easily and sometimes new features appear there first – as ToW #605 covered, with snoozing email. Check out What’s new in Excel for the web or look for the summary covering Visio, Forms, Words and more, here.
If you like being browser based rather than desktop bound
|
Tag: browser
615 – Zooming images on webpages
![]() If you’re using a trackpad rather than a rodent, or have a proper touch-screen, pinching with thumb and forefinger might well do the same thing, though exactly how will be determined by your machine’s settings. Annoyingly, some websites (like eBay, many estate agents, photo galleries etc) have a habit of not zooming into the image when you make the browser try to scale the page up; they might even make the menus and surrounding text massive, while keeping the image the same size.
A simple way to over-ride the issue might be to right-click on the image and choose to Some sites (like image libraries or photographers’ websites) won’t let you right-click on an image to save it or do anything. But there is another way… If you care to delve into the Developer Tools section in Edge (or Chrome) then you’ll get a frankly bewildering array of tools that let you peek into how the content of the page is set out and even how the site is performing over the network. Of particular interest here, though, is to be found under the Elements tab – this shows a hierarchical representation of the code behind the page, with sections that can be expanded and collapsed by a little arrow to the left of each. [Browsers other than Edge or Chrome may behave differently and call it something else – if you’re weird enough to still use Firefox, it’s Inspector vs Elements]. Normally, you’d be looking somewhere in the body section, and when you hover your mouse over an element, it will highlight that section on the page so you know you’re dealing with the right one. You’ll probably need to drill in to quite a number of <div> or <table> tags to find the one you want, though if you right-click on a part of the page and choose Inspect, it might jump straight to that particular clause . Try it on a fairly simple website and you’ll get the gist quickly. If you find an image file listed in the site coding, hover that section and you should see the properties of the image (depending on how it’s encoded); click the Current source URL and it will launch that image in its own tab. Press 12 again to close Developer Tools and return to normal browsing. |
557 – Making URLs more friendly
Early browsers might have been pedantic about the user entering the protocol into the address box, since the application wouldn’t know if you wanted to use ftp, gopher or this new-fangled http thing to try to open the page. So you had to spell out the whole address – with the right number of slashes and colons, sometimes even having to get upper and lower case parts of it exactly correct – or just get denied. Of course, it’s easier to enter URLs these days – a good proportion of end users just type the thing they’re looking for (eg “bbc news”) into the address bar, and it will search on their favourite engine to display a list of results upon which they then click. Others will know that if you enter a term in the address bar and press CTRL+ENTER, the browser will add the www and the .com to either side of it, and on Chrome, the Still, pasting a URL into a document or email can sometimes look messy, especially if it’s a link to a file on a Sharepoint or Teams site. Public websites sometimes will have an address which tells the story – like https://www.upi.com/Top_News/Voices/2020/11/19/SpaceXs-Starlink-satellites-are-ruining-stargazing-for-everyone/9351605790233/ – but a new feature in Edge browser aims to make things a whole lot more friendly. In the latest versions of Edge, instead of pasting the raw address (with all of its slashes, symbols and numbers), when you add a URL into an Office document, the link will use the title of the page as the “text to display” instead of the URL itself. As a result, the UPI story above would look like “SpaceX’s Starlink satellites are ruining stargazing for everyone – UPI.com”. When pasting a link to a shared document, instead of it showing up like https://microsoft.sharepoint.com/:b:/t/Store%20Planning%20Team/EX3o-R5PRT5Kk-Ndmh5GKFgBx0OfjIWI9d4CGT4nZGi0Dw90980 or similar, Office apps will try to fetch the source document’s details and render its name as the displayed text, hiding the URL under it: If you’re sending the link in an email, it will even check if all the recipients have permission to open it, and offer to help you fix that by changing the permissions or by attaching the document instead of a link to it. This might even realise the dream that one day, people will stop emailing documents to each other and instead will use proper collaboration tools. We can but hope.
This useful feature was a preview in the Edge beta, but is now part of Edge 87 that released last week. One potential side effect, though, is if the website you’re looking at doesn’t properly manage its page title (as displayed in the browser tab), it could paste as the wrong thing: some sites might set the title when you search for something, but then not set it properly when you click through into the results. You can always right-click the link and Edit Hyperlink to fix the issue if that occurs, and hope that enough people complain to the site owner so they fix it. |
541 – shrtn ur url
In most email programs, in Word, and even in the new Yammer experience and some other web forum software, selecting some text and pressing CTRL-K lets you insert a URL under that text – so rather than saying “Flight Simulator – https://www.xbox.com/en-US/games/microsoft-flight-simulator”, you could just write “Flight Simulator”.
When it comes to sharing URLs with other people, though, you might still need the native URL
The first URL Shortening service was launched in 2002, tinyurl.com (and doesn’t the website look like a 2002 site?). The basic idea was that instead of having a 200-character URL, you could generate something that would have the form of the tinyurl domain and a random series of characters, such as https://tinyurl.com/yxtj4gft. When the user clicks the link, their browser goes to the TinyURL website and is then provided the full link to follow, and redirects to that. The primary benefit was to make it easier to share the URL, even if it’s not so memorable, however the developers later added the ability to provide a custom redirect name and, as long as nobody else has nabbed it first, you can use it – eg https://tinyurl.com/yammerofficespace. TinyURL has been overtaken by others, notably bit.ly, which Twitter switched to from having previously used TinyURL, and before later launching its own t.co. There are many others too, some connected with existing services – like the onedrive.com shortener (eg https://1drv.ms/u/s!AgMogCiKiWDFraIfifRzFKdjw4F1uQ?e=Yepjwh) which isn’t really very short, and which causes Bit.ly to get its Alans in a twist, as it seems it doesn’t like to shorten another shortener’s link.
There are some downsides to using this kind of service, potentially. What happens if the provider goes bust, or decides to start charging users where it was once free? Sites like Photobucket which started free but began charging users a “ransom” get internet warriors hot under the collar, but so far, sites like TinyURL and it’s progeny are mostly still free to use, with the operators selling aggregate data about the referrals being followed to fund their operations costs. Some shorteners decide to close down – like goo.gl – meaning there’s a risk that previously-shared short URLs won’t work in future (though in the case of Google’s shortener, they are keeping old links alive, just not allowing any new ones to be created). Similarly, if a shortener has a technical problem or security breach, it could affect the way it works – TinyURL reportedly having problems just this week.
All aka.ms links are by definition publicly accessible, but many are used to get access to sites that are for internal use, even though they exist beyond the firewall – Sharepoint sites, for example, or the intranet homepage, aka.ms/msw. Anyone could resolve the destination URL – even en masse as one enterprise developer has done, using Azure functions – but you still need to provide appropriate credentials to access the destination site. |
519 – Browser battles revisited
Still, Edge’s recent release using the Chromium rendering engine – designed to make it comparable with Chrome from a compatibility point of view, yet allowing Microsoft developers to remove Google-services-specific stuff (and replace them, sometimes, with Microsoft-services-specific stuff, many of which will be checked in to the Chromium open-source project. The Edge browser built on Chromium was released in January, and updates are flowing through to add more functionality – which, exactly, depending on whether you’re running the normal release or you’re on one of several preview or developer (“canary”) versions. Some features are things that were ideally intended to make it to the public release – like synchronizing extensions installed across multiple PCs. The Edge update won’t be forced out to existing non-Chromium-Edge users (hello, out there!) – or at least there will be a way of stopping it from being pushed out, if you’re an enterprise IT controller who’d rather not have to manage change and things like that. One of the benefits of Edge being on Chromium is that the extensions which third parties build for the browser should be compatible – and since Google has 2/3rd of the total market, there are more of them than for other browsers. There’s an Edge “addons” page which shows a curated list of extensions known to work well with the new Edge, but if you want, you can install anything that’s listed on the Google site. If you enable the ability to install Chrome extensions into Edge, then refresh/browse to the Chrome store again, you’ll be met with scary warnings, however… Google has started alerting of a security issue – namely, if the extension is somehow added to the Chrome store and subsequently found to be of dubious intent and posing a security risk, then Google can remotely knobble it on installed machines. They are now warning that if you happen to use a Chromium but-not-Chrome browser – like Edge – then they won’t do this. It seems the extension security scare banner isn’t the only one to try to make Edge users install and switch to Chrome. Also, the Edge browsers published for Android and iOS are receiving updates to make them work more seamlessly with desktop Edge. (See more for Android & iOS) |
# 513 – Ship ahoy!
Back in the day, Microsoft nerds (yes, there were some, both in and outside of the company) used to take pride in continually referring to products by their code names long after they’d been released, and by using the most Microspeak. There used to be a browsable Microspeak Glossary on the Microsoft intranet, and various versions of it online, but they now seem to have withered. The odd phrase still crops up in contemporary usage, and one which shows its age is RTM. Historically, at a point in a software product’s lifecycle, the team just needs to ship the thing – some would think it’s the completion of the development, but most developers know nothing is ever finished and therefore nothing would ever ship. Instead, it’s some date that’s been decided, and they work backwards from that date to ship whatever they have at that point. In traditional boxed-software sales, that would mean sending the final code off to be turned into floppy discs, CDs, whatever – in other words, release it to manufacturing. RTM in the CD-era often referred to the “gold code”, as it was burned to a (gold-coloured) recordable CD before being sent to the manufacturing process. So RTM also means the final build of code as well as the process to release it. Since nobody really buys software on physical media anymore, RTM is something of an anachronism. “RTW” was used for a while, meaning “Release to Web” but it’s a clunky phrase, and has disappeared from use – much like Cisco’s attempt to for a while to talk not about “IoT,” but “Internet of Everything” or “IoE”. Nowadays, products at the end of their development cycle “go GA” – Generally Available. Much easier.
If you currently use Edge – or shudder, still use Internet Explorer – then installing the new Edge will migrate your settings, history, passwords etc, but not any extensions you might have. Fear not, though, for the Chromium engine means you can install extensions from both the Microsoft Store and also the Chrome Store too. For more on the new Edge, see the tips that are shown as part of the install process, read some opinion pieces on whether world+dog seems to think this is a good thing; here, here, here … and here… and, oh, you get the idea. |