-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Darkening Working Partially Report (Priority level: High) #6
Comments
Hi, i'm very interesterd by this kind of "Working Partially" |
Next version will be able to darken backgrounds |
Hi there @ThomazPom ! I'll wait for the next version, and then I will start a complete new set of tests, reporting to you any issues (if I find). I promise I'll be specially focused on your request for "working partially' pages. Big hug! : ) PS: Changing subject, have you ever used the Firefox' about:preference => Language and Appearance => Colors? In terms of browser performance, this is the most efficient webpage darkening tool (same RAM/CPU consumption than white webpages, no white-flashing before loading, amazing webpage loading speed, no breakages, works for 99% of the webpages etc). And in about:config you can make any change you want, for example: However, what are the cons?
If one day a Dev (like you) finds a way to use this Firefox' internal darkening tool, I believe this will be the best of the best among other similar tools. |
Note; |
I now have very nice colors and white logos |
This comment was marked as resolved.
This comment was marked as resolved.
1.2.3 is online :) |
1.2.3 is slow.. 1.2.4 will fix this |
1.2.4 is waaaaaaay faster lol |
1.3.0 is online. You should see no changes as i did not worked on darkening. However i worked a lot on page speed. |
Hi Genius! : ) Have a nice Saturday! : ) |
I believe this is due to browser cache. According to I have to use On line 192 of background.js |
You're so busy with many other priorities, that I didn't want to touch the "cache" subject. Yeah, I know cache was great years ago, when hardware and internet connection were bad. And I also know lot of users, specially those users that can't spent money, they use old hardware and lousy internet connections, yeah, I understand that cache is still useful for lot of users. I don't know if here we are talking about the same cache. Perhaps, the UltimaDark cache is different than browser cache or device cache etc. But if it is the same cache, regarding the trending of better hardware/connections, perhaps in this case cache is not needed for UltimaDark. |
We are talking about browser cache. I did not use this browser cache on purpose for Ultimadark (and i am forced to), and it needs that single code line to flush it when UDark state change (enables, disable, list edit...) |
1.3.2 should solve cache issues |
1.3.3 fixes a mistake causing the stackoverflow.com regression (and probalbly other websites) |
Works partially, darkens search box and buttons, but makes text harder to read. https://manjaro.org/ |
This comment was marked as resolved.
This comment was marked as resolved.
Top menu switches to white after scrolling and remains white: https://gearvr.net/wanted edit: still broken in 1.5.37 and 1.5.38 Top of page has a large white section but briefly flashes to the correct coloring before reverting to white: https://www.tenforums.com/graphic-cards/200306-how-reduce-laptop-brightness-below-minimum.html edit: resolved in 1.5.37 |
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
(Requires login) some popup menus are not recolored https://www.kanbantool.com |
Soundcloud player, comment boxes, and popups are failing to be recolored. https://soundcloud.com/helious-music |
Soundcloud is an app using Service_Workers I have to study how to catch their resources too. The test is simple :
|
Giant black blob in the middle of the page on 1.5.28, no clue why. Also present under 1.5.34 Update: when clicking the blob (which appears to be a broken version of the pateron logo which is supposed to be in the upper left) and then clicking back after that page loads, it goes back to normal with the patreon logo being in the upper left again where it belongs. This leads me to believe it is an ImageEdition bug. Update: Giant black blob is now white 1.5.37 LogLoaded html https://www.patreon.com/ArgusVRC background.js:2620:15 |
This comment was marked as resolved.
This comment was marked as resolved.
Confirmed broken on 1.5.33, 1.5.32 (1.5.30), 1.5.31, 1.5.28 https://www.omnicalculator.com/math/percentage-decrease |
This comment was marked as resolved.
This comment was marked as resolved.
Image edition bug ( white image as background ) |
Image edition bug ( white image as background ) |
Same issue as https://developer.chrome.com/docs/extensions/reference/api/webRequest?hl=en |
https://voyglasses.com/pages/tunable-vr-inserts broken with and without ImageEdition enabled. |
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
myforex.hpage.com/aquarius.html is a legacy html4 website, 1..5.38 yet to be released fixes html4 websites |
https://www.joshuaweissman.com/all-recipes striping dark grey and black at the bottom of the site on 1.5.38 along with miscellaneous contrast text issues. Looks like a CSS parsing error. |
Collection of All Broken Sites as of Version 1.5.40 (with checkboxes for easier review)
|
|
Here is the JS code to identify cached content of service workers // Function to list all caches, find all resources cached by service workers, and log their content type and content in a table
async function listAllCachesAndResourcesWithContentType() {
try {
// Get the list of all cache names
const cacheNames = await caches.keys();
console.log('All Cache Names:', cacheNames);
// Array to hold data for console.table
const resourcesData = [];
// Iterate over each cache
for (const cacheName of cacheNames) {
// Open the cache
const cache = await caches.open(cacheName);
// Get all requests (resources) cached in the cache
const cachedRequests = await cache.keys();
// Iterate over each cached request to gather its URL, content type, and content
for (const request of cachedRequests) {
// Fetch the cached response
const response = await cache.match(request);
if (response) {
// Get the content type from the response headers
const contentType = response.headers.get('Content-Type');
// Clone the response to avoid disturbing the original
const responseClone = response.clone();
// Read the content as text
const content = await responseClone.text();
// Add data to the resourcesData array
resourcesData.push({
URL: request.url,
'Content-Type': contentType,
'Content Preview': content.substring(0, 100) + '...' // Truncate to the first 100 characters
});
} else {
resourcesData.push({
URL: request.url,
'Content-Type': 'Not Found',
'Content Preview': 'No content found'
});
}
}
}
// Display the collected data in a table format
console.table(resourcesData);
} catch (error) {
console.error('Error listing caches and resources:', error);
}
}
// Call the function
listAllCachesAndResourcesWithContentType(); |
Thank you. Was it permanent even with CTRL+Shift+R? |
yessir |
No description provided.
The text was updated successfully, but these errors were encountered: