Lesson plan

SlimBrowser

SlimBrowser is a tabbed multiple-site web browser from FlashPeak, Inc., an Austin, Texas-based company. It formerly used the Microsoft Trident layout engine. It incorporates a large collection of features like built-in popup killer, skinned window frame, form filler, site group, quick-search, auto login, hidden sites, built-in commands and scripting, online translation, script error suppression, blacklist/whitelist filtering, and URL Alias. SlimBrowser was one of the twelve browser choices offered to European Economic Area users of Microsoft Windows in 2010. Since V6.0, SlimBrowser has adopted a multi-process architecture to improve stability and eliminate performance restrictions associated with traditional single-process browsers. SlimBrowser included a full-featured form filler with the support of multiple identities in V6.01. After development had been paused, it started again in 2019, switching to Gecko engine, counting versions from V10.0.

Back to article

Article summary

SlimBrowser is a tabbed multiple-site web browser from FlashPeak, Inc., an Austin, Texas-based company. It formerly used the Microsoft Trident layout engine. It incorporates a large collection of features like built-in popup killer, skinned window frame, form filler, site group, quick-search, auto login, hidden sites, built-in commands and scripting, online translation, script error suppression, blacklist/whitelist filtering, and URL Alias. SlimBrowser was one of the twelve browser choices offered to European Economic Area users of Microsoft Windows in 2010. Since V6.0, SlimBrowser has adopted a multi-process architecture to improve stability and eliminate performance restrictions associated with traditional single-process browsers. SlimBrowser included a full-featured form filler with the support of multiple identities in V6.01. After development had been paused, it started again in 2019, switching to Gecko engine, counting versions from V10.0.

Key claims

No claims recorded.

Discussion questions

  1. Summarise the article in your own words. Which single claim would you verify first, and why?
  2. Which claim in this article is most likely to be revised as the sources update? How would you check its current status?
  3. If two sources disagreed about one of these facts, what would you need in order to trust one over the other?

Bibliography

No sources recorded.

Key claims and bibliography are generated from the same tracked claims and sources as the article page.