Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


siria

Member
  • Content Count

    412
  • Donations

    $0.00 
  • Joined

  • Last visited

  • Days Won

    9

siria last won the day on July 5

siria had the most liked content!

Community Reputation

216 Excellent

1 Follower

About siria

Profile Information

  • OS
    none specified
  • Country

Flags

  • Country Flag

Recent Profile Visitors

2,143 profile views
  1. Just curious, regarding possible workarounds (can't test myself, old browser): does this new layout still contain the direct video links in html source code? Especially easy in meta tag "og:video". And futher down are SD and HD variations. In whichever version they send me, those links still work for downloading. If giving a timestamp error, must just replace "&" with "&". Suppose a little userscript can also wrap those links into a simple html5 video tag .
  2. Well, as RainyShadow already mentioned, after 11 pages it's a bit late to suddenly convert a general topic into a very restricted one: From "old browsers" to: - only Firefox and Chrome - only on XP - AND only their LATEST version for XP that's neglecting "XP" again, and "latest version".... .
  3. Working gmail homepage on DOS, with a DOS browser?? Absolutely incredible! Oh well, am probably not sys-savvy enough to even get a network connection, and should spend my time with UPdate stuff not downgrades, but even sitting on the sidelines it's fascinating just to know that's possible at all! A few screenshots would be nice. Hint: the current title is completely misleading. As is the name of the browser itself of course. "Links" - what a non-name, sigh... At any rate everyone who'll see this topic in the list and reading "Links for DOS Community Edition" is made to think this topic were for "Hyperlinks to some forked DOS-system" Title should somehow indicate this is actually about a DOS-browser with TLS1.2
  4. No need to hurry... KM-Goanna76 shares the same engine with NM27, and this "BigChange" build (which should IMO get a little version-number update) seems to have some severe new bugs: http://kmeleonbrowser.org/forum/read.php?19,148500,153121#msg-153121 .
  5. Whoa, sounds like not just 1, but 3 major upstream disasters. Don't get why MT is out for revenge again without any obvious trigger so suddenly - just because, as he mentioned, he doesn't like the new branding "BNavigator", saying it lacks imagination?! And he even broke NM27 (=KG76) too? Frankly I'd have more trust in new builds that just have "about:permissions" fixed, before merging tons more of (possibly questionable?) upstream updates .
  6. Undeservedly - har har... King of flaming rather. Long-standing member? May be. But the irony is the "track record" is true acc. statistics: who else here has a likes/postings ratio of even close to 1.5?? (115 Likes / 75 posts) Which also gives him an "excellent" reputation on the profile. Everyone who hasn't actually read his old postings WILL be convinced he's one of the most liked members here, and not believe anyone who dares to claim otherwise. Every time I saw this likes-ratio I couldn't help but being reminded of Einstein too, this is SO much how today's society works. Since no dis-likes are allowed of course, that would hurt the feelings of such poor, highly sensible attackers too much. Who surely have only turned evil because they had a very rough childhood etc., or people confuse aggressive narcissists and dangerous psychos with mostly nice Aspergers who do NOT enjoy harming others, etc., but I digress ;P Anyway, bans are rarely forever, and he's an important coder, am sure he'll be back again some day. Provided he wants to. At least he's very frank about his mindset. (Contrary to most other similar people, passing as Saints doing just incredibly "dumb" things unintentionally. All the time.) The good thing for me personally, have learned from this addons-issue two technical tricks: 1) those pesky CLOUDFLARE errors 502 etc. do NOT necessarily mean any REAL server probs!! It's possible, but just as well they can be created intentionally by website authors, even simply based on useragents or other settings. Actually this was the second such case in a week. 2) Important page content or even complete pages may also be hidden inside <template> tags, just like the popular SVG-wrapping trick. Users getting to see only an empty page, or mostly empty. Funny thing is, my old browser doesn't even know this tag yet, so renders it visible anyway. Normally. But awhile back had the brilliant idea to add a few "modern" tags to its global html.css, such as <mark> (for yellow background), but also <template> and <datalist>. The last two are set to "display:none" in modern browsers, so after a bit hesitation I just copied that too. Oops. Now old JS-engine didn't make the addons-page appear either. Still empty. => Now my user css file contains this: template {display: block !important;} HA: page appeared (yesterday), no javascript needed (if users do have javascript enabled, on a younger browser, I suppose they may get double-content this way, but no idea) ----- General trick: Anyone else who must browse without JS, and running into empty pages all the time? Usually killing styles helps, but not always. My LONG version of the above css: svg[style*="display: none"], svg[style*="visibility: hidden"], template, datalist{ display: block !important; visibility: visible !important; position: relative !important; width: auto !important; height: auto !important; pointer-events: auto !important; border: 4px dashed gray !important; } Ideally defined for certain domains only, if wrapped into @-moz-document.... rules. Personally have it as global rule, but this only makes sense if javascript is usually OFF. And be aware of possible false positives, of course this can just as well mess the look of some pages. Can be added in userContent.css or adblock.css .
  7. 1 line is enough, that's also usual :) /* border: 4px dashed red !important; */ Just did some more experimenting, and delighted to find this hack really WORKS to easily disable/break/ignore any amount of stuff in my complicated 200kb css-file, no matter the content! Simply wrapping a whole bunch of code+comment blocks into new Begin/End markers like this: @@comment{ ....CSS to hide.... } Even half the file or more without any worries about the engine "guessing" wrong End points
  8. CSS COMMENT syntax Had to look this up now, but the only valid comment syntax in CSS is still /*....*/ Although amazingly a javascript 1 line comment // seemed to work too when I now tested it. That would have been much handier. But after googling around, in CSS this is not treated as comment, but actually as error, and depending on the text content it may break next lines too. Pity! This page explains it in detail: https://www.xanthir.com/b4U10 To sum up: // 1-line comments like in JS: Only SEEMS to work at first, but in fact are treated as errors, and linebreaks are not the end of it. // => ignores single rules until next semicolon, or if placed before a whole ruleset, ignores it until next "}" So // can work as lazy hack for RULES (2 chars // instead of 4 /* */), if aware. But messy with free TEXT comments, still stops only at next ";" or "}" A text comment could still be ended by typing a semicolon or {}, but that's already 3-4 chars again, no gain HA! But some commenters on that blog pointed out that this could still be a brilliant hack to get NESTED comments! I often ran into that stupid prob: a longer css code block with shattered text comments here and there, and then I want to temporarily disable the whole block, BUT: with normal syntax not possible. First had to edit every single comment inside too, a major PITA. Someone also mentioned that it doesn't matter at all if "//" is used or any other invalid stuff, one uses "@comment" => Hehe, will now definitely start using this great trick! Just not quite sure yet which error-chars to use exactly, needs a bit more playing. Doing a page search for double-slashes will find hundreds of hits inside URLs, but "@comment" could simply be put at beginning of a whole block. Hmm, but there's a catch, this breaks syntax-highlighting in NPP, still displayed like active code. Too bad... Or may simply use @@ instead of // to comment out just short single rules like @@border ? Will have to test this awhile... At any rate it's important to REMEMBER such hacks if used.
  9. TechnoRelic said: > Ideally though, I would like the BNAVIGATOR Browser to 'pop open' that dialog > where it ASKS you if you want to SET it as the DEFAULT Browser ... Of course, but that goes without saying. It's not an open question whether or not that will "ideally" happen. Don't worry, work on it is currently in progress (among other things), and just a matter of time until finished. Did you notice this was explained already? Actually, twice... or was it three times... It's a bit strange that you keep pushing roytam, although you say you're happy enough using another browser in the meantime, so why... You want him to do double work? To hurry this up, as an urgent top priority? Perhaps he'll speed it up, or not, but for us end users it makes no difference whether it's done upstream or downstream ;-)
  10. MT: Well possible some of us are not the brightest here when it comes to computer science, but the fault for this misunderstanding here is your's. Not indicating what you're talking about exactly, using dev-speak, and clearly talking to RT in first post. Especially not bothering to mention to normal users who are not clairvoyant that "ShellService" might have anything to do with "Set Default Browser". That's absolutely not obvious, just a chance for blind guessing. Then again, it probably was your intention, to get more opportunities for jerking around. RainyShadow said: > As a last resort, you can try to use Control Panel > Folder Options > File Types > and manually change the assotiations. When using that method, this great little tool is an easier alternative: https://www.nirsoft.net/utils/file_types_manager.html One possibility for example is to open it and search inside where the current default "iceape" is used, then copy those lines for another browser. Am no expert for that stuff either, but guess at least four entries should be set: For ".html" and ".htm" and "http" and "https"
  11. Great it's added in first post, thanx :-) Just another example page: https://www.chip.de/artikel/Pfannen-Test-2020-Bratpfannen-Testsieger-bei-OeKO-TEST_146932113.html Now noticed that trick is especially helpful for a few pages, like cnn: this method keeps the graphics and tables readable, unlike complete stylekill. You're right that 8px red is too massive for general use. I made it so extreme and with visible ##infotext## since my user css is so chock full with rules (incl. tons of notes 200kB) that they can interfere with each other. For example have cyan borders around all iframes, and lime green borders around all video stuff, and all sorts of red borders for various other stuff too, confusing myself what's what ;-) Now fiddled and tested some more, and decided to make it just 4px too, like you. Just not red, instead "gray". That's more intuitive to remember among my other styles (gray=hidden). First tested 6px dotted gray, which looks best, but on sites where the text is glued to the border the dots are too hard on the eyes. Could add an additional "padding: 12px;" but better not mess too much, so returning to "dashed" again. border: 4px dashed gray Side note for tweakers: just learned today those css selectors must match the "computed" version too. For example an original style="display:none" becomes style="display: none;" and "display:none !important" becomes "display: none ! important;" .
  12. Can't believe no one (except 1) is ever using this very handy global permissions sheet, incredible. But great it can be fixed! While at it, in KMG74 it looks suspiciously the same: with "Forget about this site" in the upper right corner, and the displayed values have nothing to do with my real global default prefs in about:config (most handled by macro, or just permanently blocked) And if not too complicated (?), is there a way users of older KM versions might fix it themselves somehow?
  13. Just sharing a little CSS tweak for Retrozilla, K-Meleon1.5.4 and probably other browsers too, if you prefer to keep javascript disabled: Without javascript, certain websites are either completely empty or crucial page elements are hidden. That can be done in different ways of course. One method is an SVG-trick for hiding content. Examples: https://edition.cnn.com/interactive/2019/05/europe/finland-fake-news-intl/ https://sourceforge.net/projects/jsminnpp/files/Uni/ https://notepad-plus-plus.org/downloads/ I suppose such pages will show up when javascript is enabled... Without JS, they only show up when disabling inline-styles. Retrozilla: View > Use Style > None Retrozilla-Firefox2: View > Page Style > No Style K-Meleon: Prob, that requires an updated stylekiller macro. Have a working beta, but not ready yet for posting (another mini-macro grown to monster length, as so often, sigh) But here's a better workaround, fully automatic and also without JS: Just add a little css-tweak to your user styles. Without domain conditions there may possibly be false positives too, but had no probs so far. This CSS can be added in either .../profile/chrome/userContent.css or adblock.css (rename userContent-example.css if not yet done / In KM adblock preferred since it can be toggled on/off during session, userContent not) ---------- /* NOSCRIPT workaround for some EMPTY pages, or incomplete content, if hidden by SVG-trick: HTML is inside an invisible SVG-tag, requiring javascript to make visible. Gray dashed border and ##HIDDEN## lines are OPTIONAL gimmicks, just to see where it applies. */ svg[style*="display: none"] , svg[style*="visibility: hidden"] { display: block !important; visibility: visible !important; position: relative !important; width: auto !important; height: auto !important; pointer-events: auto !important; border: 4px dashed gray !important; } svg[style*="display: none"]:before {content: " (####HIDDEN SVG####) _ _ _ _ " ;} svg[style*="visibility: hidden"]:before {content: " (####HIDDEN SVG####) _ _ _ _ " ;} ---------- Minor catch: if you do have javascript enabled, this css is unnecessary, but can't add a condition "mark only if javascript is off" ;-) So IF you keep the optional dashed border and marker text, it will show up always, even if unnecessary. If you want to apply this to SPECIFIC DOMAINS only, wrap this around the code: ---------- @-moz-document domain(example1.com), domain(example2.com) , domain(example3.com) { .....css code above.... }
  14. Sigh, so much great stuff... which I'll probably not find anymore when needing it one day :-/ Just a little note regarding waybackmachine without JS: archived versions can be found by testing various cropped dates in URL bar. Without a starlet * in URL it needs no JS, and can not show a list, instead just opens the nearest hit. For winimize.com this was the last available version: http://web.archive.org/web/201109/http://www.winimize.com/ Later dates show the domain was for sale since 2012
  15. RT-KM1.5.4+TLS1.2: Thank you for testing! Sounds great, to me like a 99,99% chance that a previous setup-version (impossible to download without unknown direct mirror link) is only necessary due to missing VB files. So RT-KM154 could be made to work out-of-box if roytam1 would include those 2 dll's in the package. And 2) make it portable with the ini-file, which all portable 7z KM-builds had since KM1.6. And 3) if he'd compress it with an old zip-format that vanilla win98 users could uncompress without needing inaccessible SF-downloads, or better make it a self-extracting exe (which people like me who don't like exe's and already have a younger zip-tool could probably just unzip too) I think it's really necessary that there's at least 1 of his browser builds (RZ-SM, RZ-FF2, RT-KM154) as "starter build" for vanilla98+IE5 users, needing no other resources of any kind. Which can then be used to further download otherwise blocked stuff from Sourceforge, github etc, needed for all further updates. Like KernelEx, or a younger 7-zip (v9.20 for Win98) which is necessary to unzip all his other browser builds. FF3.6 (and current RT-build too) runs with basic KernelEx - you hinted somewhere considering it ;-) It's really quite a generation leap from FF2 to FF3.6, and from KM154 to KM1.6. For me most important, there sure are a lot more Firefox3.6 ADDONS as for FF2, let alone for Retrozilla-Seamonkey. And in KM the slightly younger JS-engine matters too, for macros. While I hardly ever use javascript for websites, it's still needed for lots of site-tweaks and old-engine workarounds using little macro scripts, which very often use e.g. "querySelectorAll" which just didn't exist yet in FF2/KM154. Workarounds may be possible in many cases, but very bothersome. Just today struggled yet again several hours on amazon, grmpf, dabbling with a little macro script for article pages, to get those stupid links to other "colors" working again. Which are usually not about colors at all but for all sorts of product variations. Finally works now in KM1.6, but now wasting yet more time trying to add workarounds-of-workarounds for KM154? Ouf, grmpf, no thanks, took far too much time already... By the way I finally realized I can test stuff again with "basic" KernelEx! Have a decade old version on my second disk, ancient backup, which actually still boots. It was even pre-release, KernelEx RC4, but don't dare to touch it anymore to upgrade. At any rate the crucial point about "basic" KernelEx is that it was much more stable, never gave me trouble with native Win98 apps, and was by default "off". So did a few little tests now with RT-fx36. Turned out it *does* start with basic old KernelEx compat set to "Win98"! But there's a catch, or rather two: 1) If explicitely set to "disabled", it crashes at start 2) xul.dll needs compat "Win2000", which KernelEx has automatically predefined. Otherwise display is completely messed. Toolbars invisible and transparent, pages almost empty and no text either. Typical look for missing KernelEx.
×
×
  • Create New...