Recommended Posts

I'm not sure if this will help or not, but this is the code I use to make "about:blank" transparent

#browser,
#content > tabbox > tabpanels {
  background-color: transparent !important;
}

#main-window[stylish-url="about:blank"] #content browser { 
   opacity: 0 !important;
}

Hi foxxyn8

I couldnt get this to work , i have a white background instead....does this works on windows 7 only cos i am using vista64 =p

Hi foxxyn8

I couldnt get this to work , i have a white background instead....does this works on windows 7 only cos i am using vista64 =p

that's the old code. use this instead (requires stylish):

#appcontent,
#content > tabbox > tabpanels {
  background-color: transparent !important;
}

#main-window[stylish-url="about:blank"]:not([onclose^="PrintUtils"]) #content browser { 
   opacity: 0 !important;
}

Does using stylish and having userchrome.css have any differences (startup UI responsiveness, blah blah)? I'm already satisfied with my userchrome so I'm thinking about removing stylish.

Foxxyn8 had pointed out that userChrome.css can't handle anonymous content, if I understood correctly.

The other advantages of using Stylish may be useful to beginners (moi) like previews (which have a "proof-reading" ability) and not having to restart the browser to see the effect of changes.

Foxxyn8 had pointed out that userChrome.css can't handle anonymous content, if I understood correctly.

The other advantages of using Stylish may be useful to beginners (moi) like previews (which have a "proof-reading" ability) and not having to restart the browser to see the effect of changes.

To expand on this, the difference is that userContent/Chrome are user stylesheets whereas stylish uses user agent(UA) stylesheets. The difference being, in particular, UA can apply styles to native anonymous elements and to CSS anonymous boxes.

Also stylish handles the functions of both userChrome and userContent.

As far as performance goes, I've never noticed any difference. Stylish just makes it easier all around.

Back to beg for more help. :laugh: . What do I add to grey out the favicons on the bookmark toolbar, or everywhere else for that matter? I saw some code that did it earlier in the thread, but I haven't been able to find it again.

https://www.neowin.net/forum/topic/921416-share-your-custom-firefoxminefield-4-stylish-scripts/page__view__findpost__p__593741318

I don't like "text-shadow" (or "etched" effect or anything that makes letters less clear-cut) which I see in a lot of drop-down menus and dialog boxes/panels. Is there a general way to fix that?

In userStyle.css, this works great:

* { text-shadow: none !important; }

I don't like "text-shadow" (or "etched" effect or anything that makes letters less clear-cut) which I see in a lot of drop-down menus and dialog boxes/panels. Is there a general way to fix that?

In userStyle.css, this works great:

* { text-shadow: none !important; }

I don't think it gets any more general than that. You're telling every selector not to use a text-shadow.

I don't think it gets any more general than that. You're telling every selector not to use a text-shadow.

Foxxyn8, but how do I get it to work for the UI (chrome?) of the browser (as opposed to the page content)?

I already have this as a specific example:

#FindToolbar *{ -moz-appearance: none !important; background: #333 !important; color:black !important; font-weight: bold !important; text-shadow: none !important;}

Without it, certain text (Next, Previous) in the Find Toolbar would appear "different" (blurry to me) when there is no search text entered.

So what I want to know is whether there's a universal code that can be used in my style that affects various aspects of the UI (chrome?).

(Just to be clear, I have separate styles in Stylish to reflect chrome versus content.)

I don't think it gets any more general than that. You're telling every selector not to use a text-shadow.

Interesting (and a bit alarming at first). I put the same line in my "chrome" Stylish code. And now I don't see the text-shadow effect :) . The alarming bit is that I don't see the text at all in some cases unless I hover over where it should be. This is okay sometimes but could cause panic at other times.

Interesting (and a bit alarming at first). I put the same line in my "chrome" Stylish code. And now I don't see the text-shadow effect :) . The alarming bit is that I don't see the text at all in some cases unless I hover over where it should be. This is okay sometimes but could cause panic at other times.

That's probably because the color property of the selector is the same as the background-color property. For instance if the text color is black, the background-color is black, a white text shadow makes the text visible. If you remove that text shadow the text becomes unreadable.

That's probably because the color property of the selector is the same as the background-color property. For instance if the text color is black, the background-color is black, a white text shadow makes the text visible. If you remove that text shadow the text becomes unreadable.

That is fair enough. But just out of interest, how is "inactive" text selectively shadowed? Like the example I gave for the Find Toolbar. Or another example when one views a drop-down menu such as "Edit". If no content has been copied by Ctrl+C, the Paste options are shadowed. I'm asking because I'm not sure of how to get the info with the Domain Inspector.

that's the old code. use this instead (requires stylish):

#appcontent,
#content > tabbox > tabpanels {
  background-color: transparent !important;
}

#main-window[stylish-url="about:blank"]:not([onclose^="PrintUtils"]) #content browser { 
   opacity: 0 !important;
}

Awesome!! Thnx for the pointers!

That is fair enough. But just out of interest, how is "inactive" text selectively shadowed? Like the example I gave for the Find Toolbar. Or another example when one views a drop-down menu such as "Edit". If no content has been copied by Ctrl+C, the Paste options are shadowed. I'm asking because I'm not sure of how to get the info with the Domain Inspector.

They're using the [disabled = "true"] attribute. In the right panel of DOM Inspector choose Object - DOM Node. That will show you all the attributes of the chosen selector.

post-350326-0-18854500-1302271474.png

They're using the [disabled = "true"] attribute. In the right panel of DOM Inspector choose Object - DOM Node. That will show you all the attributes of the chosen selector.

...

Thanks for the pointer :)

So now I have:

* {text-shadow: none !important}
* [disabled="true"] {color:#555!important; font-weight: bold!important}

Looks like it's going to take me a lot more time before I can learn to use DOM Inspector for less obvious things :(

Anyone can help me out with these 2 problems ?

I have a weird line and i need to get rid of it

How to change the text color of on the "NEXT" button in the FIND BAR?

Re. the second one, this works for me:

#FindToolbar .findbar-find-next {color: green!important;}

Anyone can help me out with these 2 problems ?

I have a weird line and i need to get rid of it

How to change the text color of on the "NEXT" button in the FIND BAR?

#FindToolbar .findbar-find-next:not([disabled]) {
        color: red !important;
}

#navigator-toolbox::after {
	height: 0px !important; 
}

Thanks for the pointer :)

So now I have:

* {text-shadow: none !important}
* [disabled="true"] {color:#555!important; font-weight: bold!important}

Looks like it's going to take me a lot more time before I can learn to use DOM Inspector for less obvious things :(

* [disabled="true"] 

works, but you should use

*[disabled = "true"]

Re. the second one, this works for me:

#FindToolbar .findbar-find-next {color: green!important;}

#FindToolbar .findbar-find-next:not([disabled]) {
        color: red !important;
}

#navigator-toolbox::after {
	height: 0px !important; 
}

thank you both for the help ^^!

i also managed to figured out the text color for findbar "NEXT", "PREVIOUS" and "HIGHLIGHT" button !! :laugh:

#FindToolbar toolbarbutton:not([disabled]) {
    color: #fff !important;
}

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • To give context to everybody, I bought about 2 sets of RAM, ddr4, 3200, 64 gb, 2 years ago. It costed me 150 usd for each set. If you buy RAM now you only incentivate companies to sell you expensive stuff, as Nvidia did.
    • KillerPDF 1.4.2 by Razvan Serea KillerPDF is a lightweight, portable PDF editor for Windows built for users who want full control without subscriptions, installers, or telemetry. It runs as a single executable, making it ideal for USB use and field work. You can view PDFs with smooth PDFium rendering, navigate quickly with thumbnails, zoom, and shortcuts, and reorganize pages using drag-and-drop. It supports merging multiple PDFs, splitting documents, and extracting selected pages. KillerPDF also allows inline text editing with font matching to preserve the original layout, plus annotations like text boxes, freehand drawing, highlights, and reusable signatures. You can search full text, copy content easily, and print documents with flattened annotations. Designed as a free and open alternative to bloated PDF tools, it works fully offline on Windows 10/11 x64. No runtimes install. Everything needed is inside the EXE (targets .NET Framework 4.8, which ships with every supported Windows release). KillerPDF key features: High-quality PDF rendering via PDFium Edit PDF text inline (double-click to modify text) Page thumbnails and fast navigation with zoom and shortcuts Merge multiple PDFs into one Split PDFs and extract selected pages Drag-and-drop page reordering Font matching to preserve original document appearance Text boxes for notes Freehand drawing tools Highlight overlays with adjustable color, size, opacity Undo actions and clear per-page annotations Create, draw, and save reusable signatures Click-to-place signatures anywhere Full-text search with highlighted results Drag-select or Ctrl+A to copy text Print with annotations flattened Portable single-file app (~10 MB) No installer, no admin rights required No account, no telemetry KillerPDF 1.4.2 changelog: What's new PDF form filling. Interactive PDF forms now render their fields (text inputs, checkboxes, radio buttons) as live controls. Fill them in directly and save — field values are written back into the PDF. PDF outline (bookmark) navigation. A new OUTLINES tab in the sidebar displays the document's bookmark tree. Click any entry to jump to that page. The sidebar auto-fits its width to the longest entry on open and can be dragged wider; switching back to PAGES snaps to the pages-mode width. Fixed Page rotation no longer reverts after saving. Rotations applied via the sidebar context menu now persist correctly through the save pipeline. Copied text words were out of order on PDFs where glyphs are stored in non-reading order (Issue #66). Text extraction now sorts words by position and uses a dynamic line-grouping threshold so both drag-select and Select All produce correctly ordered output. PDFs with malformed or non-standard XRef tables now open in read-only mode instead of showing "Invalid entry in XRef table" and failing entirely. Download: KillerPDF 1.4.2 | 6.1 MB (Open Source) Link: KillerPDF Home Page | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • "...a low price of just $340..." I don't think it means what you think it means.
    • This Corsair Vengeance DDR5-6000 32GB RAM with RGB is a great deal for limited time by Sayan Sen Memory prices have been through the roof for a while, though it seems like things might finally be getting better. If you are in the market for one, then grab this Corsair Vengeance DDR5 32GB (2x16GB) DDR5 6000 CL36 kit with RGB for a low price of just $340 (purchase link under the specs table down below). The kit is compatible with both AMD and Intel systems as it supports both EXPO and XMP overclocking profiles, respectively. 6000 MT/s is often the sweet spot for many systems as it provides ample data transfer speed while still being on Gear 1 mode. This Vengeance variant has RGB so if you love bright setups with such lighting, this is a win-win for you. The technical specifications of the Corsair Vengeance memory kit are given in the table below: Specification Value Memory Type DDR5 Memory Size (Total) 32GB Kit Configuration 2 × 16GB Form Factor UDIMM (Desktop) Pin Count 288-pin Speed (Data Rate) 6000 MT/s Speed Rating PC5-48000 Tested CAS Latency 38-44-44-96 Voltage (Tested) 1.35V Performance Profile AMD EXPO & Intel XMP Heat Spreader Aluminum heatspreader Cooling Type Passive (Heatsink) Lighting Ten Zone RGB Software Support Corsair iCUE Get it at the link below: CORSAIR Vengeance RGB DDR5 32GB (2 x 16GB) 6000 CL38 – Gray (CMH32GX5M1E6000Z38): $339.99 (Sold and Shipped by Woot US, Fulfilled by Amazon US) This Woot deal is US-specific and not available in other regions unless specified. This is a first-party seller link (at the time of article publishing); ensure that you also purchase from a first-party seller link only. If you don't like it or want to look at more options, check out the previous deals that we have covered, OR you can also visit Amazon US deals page. Get Prime (SNAP), Prime Video, Audible Plus or Kindle / Music Unlimited. Free for 30 days. As an Amazon Associate, we earn from qualifying purchases.
    • The very fact that a TPM (v2.0 specifically which is part of the issue I suspect) is now a baseline for any supported Windows installation will naturally mean other vendors will start to leverage it as they know it'll be there. It's called progress, and it's always been the way. A TPM isn't a windows thing, it's just a module designed to securely store keys. Secure boot isn't a Windows thing (although MS are the TCA as I recall hence the upheaval this year as the 2011 certs expire), it's just a way to verify a bootloader is signed. Windows simply leverages them.
  • Recent Achievements

    • Proficient
      Eric Biran went up a rank
      Proficient
    • Dedicated
      Conjor earned a badge
      Dedicated
    • Week One Done
      Windows Guy earned a badge
      Week One Done
    • Dedicated
      Mark Spruce earned a badge
      Dedicated
    • Collaborator
      conkir earned a badge
      Collaborator
  • Popular Contributors

    1. 1
      +primortal
      479
    2. 2
      PsYcHoKiLLa
      244
    3. 3
      Steven P.
      72
    4. 4
      +Edouard
      66
    5. 5
      Skyfrog
      65
  • Tell a friend

    Love Neowin? Tell a friend!