Skip to main content


How to fix "User must login with specified account" error on ZEE5

ZEE5 is one of the most popular video streaming platforms in India, offering a wide range of content in different languages. However, like any other platform, users may encounter errors while using it. One of the most common errors that users face while trying to log in is the "User must login with specified account" error. In this blog post, we'll explain what this error means and how you can fix it. What does the "User must login with specified account" error on ZEE5 mean? The "User must login with specified account" error appears when you're trying to log in to ZEE5 using an email ID that has been registered via social sign-up, such as Google, Facebook, or Twitter. In other words, if you've signed up for ZEE5 using your Google or Facebook account, you'll need to use the same social account to log in to ZEE5. Why does the "User must login with specified account" error on ZEE5 occur? The reason why the error occurs is that ZEE5 r

Smart Card Authentication Coming to Chromium-based Browsers like Chrome, Edge

Chromium-based web browsers including Chrome and Edge are likely to introduce support for the Web Smart Card API , a browser API that enables web applications to communicate with smart cards, Techtsp has spotted a new development. The proposed API is currently in development and is expected to be released natively on Chrome and Edge in the near future. The implementation is currently in progress, and a Chromium bug report related to the implementation suggests that it is nearing completion. Although the concrete details of the implementation are still unclear and will depend on the specific web browser and operating system being used, as well as any additional security measures or protocols that are put in place to ensure the security and privacy of users' smart card data, in general, the implementation will likely involve the following steps: The web browser will provide an API that web applications can use to interact with smart cards. This API will be based on the proposed Web A

Google Chrome 98 re-adds 'only' keyword for color-scheme by default

Starting with Google Chrome 98, the 'only' keyword has been re-added to the specification for color-scheme as a way of per-element opt-out of color-scheme override like forced darkening. Meaning, this feature can essentially be used to do per element opt-out of color-scheme overrides like forced darkening. If the user has indicated an overriding preference for a particular color scheme, and the author has not disallowed this (by using the only keyword), the user agent may override the color scheme, forcing the used color scheme to the user’s preferred color scheme. If the element does not support that color scheme, the user agent must also auto-adjust other colors into this chosen color scheme, such as by inverting their brightness, while preserving any color contrast necessary for the readability of the page. In this case, UA may also auto-adjust colors within replaced elements, background images, and other external resources as appropriate. The specifics of such auto-adjustme

Google Chrome 97 to get rid of a serious ‘security problem’ after 8 years

Starting with version 97, Google Chrome has decided to deprecate and remove what it describes as ‘a security problem' from Chromium and WebRTC. The SDES key exchange mechanism for WebRTC, which was declared Historic by the Internet Engineering Task Force (IETF) in 2013, is finally being removed from the stable Chrome version 97, which is scheduled to release on Jan 4, 2022. What is SDES key exchange mechanism? Stands for Session Description Protocol Security Descriptions, SDES for Media Streams was proposed for standardization to the IETF in 2016 as a way to negotiate the key for Secure Real-time Transport Protocol. The keys transported in the Session Description Protocol (SDP) attachment of a Session Initiation Protocol (SIP) message ensure the attachment is end-to-end encrypted so that no one else can see the attachment. The problem statement The Google Chrome team says it exposes session keys to Javascript. Therefore, entities with access to the negotiation exchange, or with the

Window Controls Overlay could render Spotify's desktop app useless

A Chrome feature that makes desktop web apps look just like native desktop applications is almost here. The upcoming feature Window Controls Overlay , which will allow web developers to turn their progressive web apps (PWAs) installed on the desktop to look just like their native counterparts, is now in the final stages of development and rollout, Techtsp has learned. As a result, Google Chrome and Microsoft Edge users will not be able to differentiate between progressive web apps and native desktop applications. One of the groundbreaking features has already made its way into version 97 (canary/dev) build and will be fully functional, with a stable release scheduled for January 4, 2022. Customized Title Bar with Window Controls Overlay The main goal behind this feature is to allow web app developers to extend the customizability options to the title bar area, similar to native desktop applications. As a result, developers can maximize screen real estate to show customized options over

[Exclusive] Google Chrome will be soon getting dedicated side search panel

Google is currently working to add a new side search panel to its Chrome desktop browser, Techtsp has spotted multiple Chromium commits confirming this new development. Apparently, this move is aimed at driving more traffic to Google Search while allowing users to continue working within the existing tab without getting distracted.  Google Chrome Side Search: What is it? Searching the web while working on some task can be a distraction at times. Therefore, Google has decided to soon allow users to search within the Chrome browser without actually navigating away from your existing tab. For instance, if you have to search the web using Google search, you will no longer have to search or navigate to within the existing tab. Instead, Google will provide users with the side search panel within the Chrome browser which will then take care of all your outbound activities. This way, Google Chrome aims to minimize additional navigations and encourage a distraction-free web browsing

Chrome working on new ‘Privacy Review’ settings

Chrome has been working on a new feature 'Privacy Review' to help users review various privacy settings, Techtsp has spotted a new development. Available behind a feature flag, this feature will serve as an entry point to new privacy checkups in the Chrome browser. Privacy Review in Chrome This new feature flag has been added to the Developer build and is disabled by default. Once enabled, it shows a new subpage under the ‘Privacy and security’ tab in Chrome. The flag description reads: “Shows a new subpage in Settings that helps the user to review various privacy settings.” How Privacy Review Chrome flag works Enabling the new #privacy-review feature flag in Chrome adds a new subpage under privacy settings called ‘Privacy and security review.’ This will help users review the most important privacy and security controls in one place. However, clicking on the new ‘privacy review’ tab did not open any new settings. It looks like the feature is not fully ready and is currently und

Now natively open files with Google Chrome, Microsoft Edge PWAs on Windows 10

Google Chrome web apps can soon express their ability to read and edit files from Windows 10’s native file system. Therefore, in addition to native apps, users can choose to open and edit certain file types with progressive web apps (PWAs) installed on Windows 10 computers. This has been made possible with the help of an upcoming feature called File Handling, Techtsp has learned. Now, similar to native apps, Google specifically wants web apps to declare their ability to handle files with given MIME file types and extensions. This way, Google says it wants to increase transparency between web apps and native apps by providing users with a more consistent user experience across both. “The goal for this project is to implement an API that will allow Chrome progressive web apps (PWAs) to 'handle' (read) files in the host OS's file system, in much the same way as a native app would,” said Google engineer Darwin Huang in a design document seen by Techtsp. “This dovetails with the

Google Chrome users can soon mute mic, turn off camera, end video calls with picture-in-picture

Google Chrome is extending Picture-in-Picture (PiP) capabilities to video conferencing actions with the help of something called Media Session API , has spotted a new development. This feature has not shipped to any Chrome channel and is only being prototyped at the moment. This feature will allow users to easily mute their microphone, enable/disable the camera, or end their conference calls using a PiP window. has also obtained an early UX mockup of the feature. "We want to make picture-in-picture (PIP) more useful on video conferencing platforms by enabling the user to mute/unmute their microphone, enable/disable their camera, or hang up the call from the PIP window. To accomplish this, we’ll add new actions for these to the MediaSession API and let websites declare handlers for those actions," said Google engineer Tommy Steimel in a design document seen by This functionality is mostly applicable with Desktop platforms, including Linux,

Microsoft Edge PWAs will soon be visually indistinguishable from native apps

Microsoft Edge will soon introduce a new feature called  Window Controls Overlay to make Progressive Web Apps (PWAs) visually indistinguishable from their native counterparts, enabling developers to customize the title bar area of their PWAs. [Listen to this article on Spotify] "This feature enables developers to build web apps which make better use of screen space and allows them to design their app to feel more like a native app. As devices become smaller for portability, the title bar consumes a larger fraction of the screen, leaving less room for the user to interact with the app," Microsoft Edge's Amanda Baker said in a technical document seen by Techtsp. Edge is trying to solve one of the biggest problems with Progressive Web Apps: the lack of customization of the title bar area. Unlike native apps, which come with a customizable title bar, PWAs have a title bar section reserved by the system. As a result, PWAs end up looking like they are running on in a separate