Is there a browser designed for dark mode or night mode. Besides Chrome or Firefox, they both have bugs for this design. Chrome has a flashing white screen on every page load and Firefox is unable to log in to Hotmail. A browser specifically designed for night mode would be ideal for Windows 10 64-bit.
I have Firefox on Windows 10 64-bits, with this add-on Dark Mode and almost every web-page is well displayed with a dark smooth that you can customize (with lots of dark colors), and even better it lets sites such as YouTube to display their own dark mode.
Also I can login to Hotmail with no problems
You only have to click on the slim bar to type your username
You can use Vivaldi, which is made for completely customized color schemes. Additionally, if you want to enhance chrome or Vivaldi (which can use Chrome-Addons) you could install Dark-Reader.
Related
I've just loaded FF onto a new Macbook Pro (Monterey), and have also recently signed up for Firefox Sync - to import bookmarks, passwords, etc into this new installation. I'm perplexed at what I'm seeing on the new machine, though. I have the firewall on, all Sharing settings off, Bluetooth off, wifi off. No ethernet. The machine is hypothetically completely air-gapped.
But the new machine is displaying the Firefox sync icon (superimposed on the logo is a little picture of a laptop, hovering over it says "from laptop"). This icon appears when I open Firefox on the old machine. It's very unsettling. Nothing on the new machine indicates there should be any communication between FF instances.
Can anyone tell me how this would be happening? Is there some undisclosed p2p action going on between the machines based on physical proximity?
This appears to be an Apple OS feature called "Handoff". It works with multiple browsers, and offers to share browser tabs between your devices through iCloud, apparently. It also does clipboard sharing, and some other things.
It can be disabled through System Preferences > General > uncheck "Allow Handoff between this Mac and your iCloud devices". (For more: https://howchoo.com/macos/how-to-disable-chrome-tab-sharing-handoff-in-macos - article is about Chrome, but this seems to work with Firefox as well)
I have no explanation how your machine was still communicating with all the networking interfaces apparently turned off, though.
When I use the Chrome DevTools debugger to debug a chromecast custom receiver the screen is green.
I have disabled hardware acceleration in Chrome. This happens on both Windows and Mac. It happens from all PCs in my home.
No error messages are provided. Here is what it looks like.
Sir i think there might be something wrong with the chromecast,
i had the similiar issue here.
i want to debug webview app using emulator and it just shows green screen but i still tap on the screen. then i using real device to test my app and it works. it shows the page how it should be.
I wanted to develop my own watchface for my Gear S2. I found some good documentation on downloading and using the Tizen IDE. All is well, but I'm finding the tweak css/html5-run/upload-switch faces-view-wash-rinse-repeat to be very tedious and time-consuming.
I know I can point my browser (Chrome) to my development workspace and load the index.html up and I surmise that I could tweak what I have, which came from the template to work in the browser if I made the sizes in the css static vs dynamic (absolute vs percentages). But is there a better way? Scouring the Internets Googles have yielded nothing too helpful yet.
moderators: this might be OT for this particular SO. If that's the case, I apologize. A nudge in the right direction would be greatly appreciated, if so.
So, I was able to make a little progress on this myself. I am using Chrome in developer mode, which almost works perfectly when using the developer device emulator. To toggle the device emulator, open developer mode (windows: ctrl+shift+I, OS X: cmd+option+i) and when the tool window opens up, look for the little device button next to the element button in the upper left corner of the developer tools window. When the device emulator open, switch the resolution to 320x320 (top of the window next to "screen").
Now, open your index.html file for your project in Chrome, and you can at least muck around with your css styling.
Now to get around the whole issue of reloading your clock with the default clock in the Java emulator for Tizen, I was able to get my changes to automatically assert when running the new code. The way I did it, though I'm not sure if all of these steps were necessary was:
In the emulated watch:
1. set the screen timeout to 15 mins.
2. set the watch face to your development watch face
In the IDE:
1. when ready, use the button for smart launch (it's the blue button just to the left of the bug button in the tizen web IDE). This is in the Tizen SDK version 2.3.1 build 20150721-1440.
At the time of running your code -- making sure both your emulated watch is running too:
1. In the IDE, click the smart launch button
2. Click over to your emulated watch and make sure it's in focus.
It should update the watch face with your latest changes in realtime. This worked for me, so YMMV, but at least I didn't have to reload the watch face after asserting the latest version.
I have been finding the way to get the urls of opened tabs of the browsers of Firefox and Chrome using Accessibiltiy.
I found that Firefox can get the urls using at-spi, but Chrome can get the url of focused tab a few months ago.
I have gotten a new result recently during the test. It is that I cannot access the child of Chrome using Accessibility, so I don't even know the url of focused tab.
"atspi_accessible_get_child_count" returns 0.
But as I said earlier, it worked on Chrome 31 version.
According to Assistive technology support, there are not tools to test accessibility in Linux.
Chrome does not support Accessibility anymore?
There is the answer in Chrome Accessibility.
That says accessibility of Chromium on desktop Linux is not really supported currently.
You need to start Chrome like this:
ACCESSIBILITY_ENABLED=1 chrome --force-renderer-accessibility
Both of these are necessary. For electron apps, ACCESSIBILITY_ENABLED=1 seems to be enough, at least that was the case with VSCodium and Signal Desktop.
On Windows, this is not necessary because a11y enables itself once a known screen reader is detected (afaik), but Orca under Linux is apparently not known.
I know about firebug and the developer tools for the major modern desktop browsers, but I can't find any way of debugging JavaScript code on mobile browsers.
What are some high level techniques I can use to debug code on mobile browsers?
Android devices can be put into developer mode by going through settings>Phone status then tapping on "Build number" 7 times. This allows you to do a bunch of things (see step 5) including USB debugging. (Some devices might have Build number under Software Info)
To activate USB debugging, look in Settings for the newly appeared "{ } Developer Options", open this and switch on USB debugging. Connect your device using a direct USB connection.
In Chrome on your desktop, in the usual developer tools panel used for debugging, look in the menu for more tools>remote devices. With Discover USB devices selected, you should now see your mobile device on the side.
Select it to see a list of all the chrome tabs you have open and the ability to enter URLs directly.
Selecting one of the links will open up a new window with a mirror of your device screen on the left and all the familiar chrome debug tools on the right. You can still control your device directly or use the mouse on the mirrored screen. It even rotates.
full details on remote debugging from google and how to enable developer mode (link as above) from askvg.com
Android provides a tool set for these purposes:
https://developers.google.com/web/tools/chrome-devtools/remote-debugging/?utm_source=dcc&utm_medium=redirect&utm_campaign=2016q3
Apple does it a similar way:
https://developer.apple.com/safari/tools/
Tutorial: https://css-tricks.com/using-chrome-devtools-to-debug-javascript-in-any-browser-with-ghostlab-2/
You can debug on Safari Mobile with any iPhone/iPad. In Developer menu you can find your device and you can then debug your code with inspector.
If you have an Android Device instead, you can debug on Chrome Desktop (remember to active the debug mode) with chrome://inspect
On the IPhone you can go into settings>Safari>advanced and turn web inspector on
Sometimes I get bugs reported by customers that are not reproducible every time or in our testing. For such cases I recommend Lucky Orange. It records the user activity and also has the option to record console messages.
PS - I'm not an affiliate, I use them for my own projects and like it.
Another solution for basic debugging (which many times is all is needed), is having a console polyfill on mobile without the need to plug into USB on desktop.
mobileConsole is such a console polyfill.
Hope it helps someone, I found it useful.