The last version of Internet Explorer, version 11, was released on October 17, 2013. This is a very long time ago when taking into account the rapid development of web technologies. These days it is often difficult and time consuming to get modern technologies to work well in this old browser. More and more frameworks are dropping support, and even Microsoft themselves has announced that they will fully drop support for IE in their own services in 2021.
Consequently, we have decided to not include support for IE in the Design Library website.
When you are going to create a micro-frontend page, you need know what guidelines there are for an internal or/and an external shell.
The shells share common functionality as much as possible if they have the same need, but there is also separate functionality for each shell.
The navigation structure is used by all shells, but Nexus are also using the navigation to view out the customer holdings.
The Profile selector is used by all shells. When you expand the Profile selector, you’ll find settings for the customer/employee.
You’ll find the Language selector under the Profile selector. This is a common functionality for all shells. The customer/employee selects a language and the selection appears on all connected Micro frontend pages. It’s the Micro frontend owner’s responsibility to build the language choices that connects to the shells Language selector.
In the Nexus shell you’ll find a Customer selector. The employee can start to write in letters/numbers (name, social security number, org.name/number) for a customer and a relevant search result will appear. When the employee has found the right customer, he/she can click on the whole customer area.
Nexus is collaborating with other teams like Advisory to find the best content for our employee needs.
Implementation of headings is especially important for people using assistive technologies. Web content must be semantically structured to be programmatically determinable in a meaningful way.
What is the recommendation from the shells when it comes to making sure that any CSS spills over from a MFE up to the shell?
MFE's use unique classes on their base node in MFE DOM and wraps all CSS within it. This protects it from any "spillage".