Browser (cat)
Texas library cat
Browser was an American library cat that lived in the White Settlement Public Library, near Fort Worth, Texas, United States. In July 2016, Browser was evicted from the library by the local municipality, provoking an international backlash that resulted in a re-vote, and a unanimous decision permitting him to stay.
Browser died on September 3, 2025 of natural causes.
Eviction attempt
Browser, a grey tabby, was adopted by White Settlement Public Library from a local animal shelter in October 2010. Originally he was obtained to control rodents, but later became a popular mascot of the library among patrons, even featuring in the library's fundraising calendar.
On June 14, 2016, White Settlement City Council voted by a majority of two to one votes to remove Browser from the library. The removal motion was made by councillor Elzie Clements, who claimed, “City Hall and City businesses are no place for animals”, and council member Paul Moore, who was primarily concerned about triggering people with allergies to cats. Mayor Ron White claimed that the motion to remove Browser was a response to a council worker not being permitted to bring his puppy to City Hall.
Later developments
In response to the eviction decision, a petition to permit Browser to remain in the library attracted over 12,000 signatures worldwide, and Mayor White received over 1,500 emails advocating for Browser to be permitted to remain in the library. On July 1, 2016, White Settlement City Council unanimously voted to reverse its earlier eviction decision.
This brief starts where responsible research should: with the source description of “Browser (cat)” as texas library cat. Everything that follows is an evidence route, not borrowed authority.
Why this record matters
The subject matters to the places & architecture register because the source frames it as texas library cat. Its deeper value depends on whether names, dates, institutions and citations support that framing.
Place names and jurisdictional language are key evidence: both can reveal earlier catalogue descriptions and overlooked record series. The source revision retrieved here is dated Aug 18, 2026. The linked authority identifier is Q116233237. None of the 0 selected statements returned an explicit reference. The first chronological checks are 2016, 2025 and 2010.
A single description cannot reconcile every naming convention, rebuilding phase or administrative transfer associated with a place. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Treat names, boundaries and functions as historically changeable. Maps, plans, inventories and administrative records can clarify what the place meant at different dates.
- Historic place names
- Jurisdictional context
- Routes into maps and plans
Contemporary maps, plans, listed-building records, estate papers and the responsible local or national archive.
Three-step research path
- Establish the record: confirm the title “Browser (cat)”, its source revision and the description used here.
- Expand the search: follow Browser (cat) primary sources, Browser (cat) archive and Browser research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Browser (cat)”?
- Which authority defined the place, boundary or structure at the relevant date?
- What physical evidence or contemporary plan supports the description?
Search terms from this dossier
This entry incorporates text from “Browser (cat)” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.