Microsoft begs Web devs not to make WebKit the new IE6


Recommended Posts

Given that Chrome is faster than any other browser on Windows their approach seems to be working, obviously lack of D3D support isn't holding them back.

Erm Chrome and Firefox does use DirectX/D3D via the ANGLE Project, which transforms WebGL into DirectX calls.

I guess you have to be special type of blind to miss the irony and hypocrisy in this..

And yet you're preaching on about how right it is for them to be doing the exact same thing? Open source or not, breaking standards is bad.

Only a problem if your browser isn't properly sandboxed. WebGL is no more dangerous than any of the other 2D or 3D acceleration APIs built into modern web browsers. And DirectX is a "standard" because Microsoft give incentives to game studios to leverage it. Google don't support it because Chrome is a cross platform browser, and it's easier to port code from one platform to another if you use the same API on each. Given that Chrome is faster than any other browser on Windows their approach seems to be working, obviously lack of D3D support isn't holding them back. Besides, the web relies on open source technologies, and Microsoft's 3D and 2D api's aren't open source, making them useless to web developers. I don't. I'm just tired of hearing Microsoft shills blathering on as if every company and person on the web has some obligation to design everything around their products.

Not as tired as I am of seeing you call everyone who disagrees with you a shill. If you haven't got an argument and need to rely on abuse it would probably be best if you just don't post.

HTML5 test is not a valid benchmark. It tests things which are out of spec.

AFAIK, it doesn't even test anything but just queries if the browser supports it.

Bingo. HTML5 test is only useful for marketing departments, you need test cases to measure conformance - you can't just test for existence and hope for the best.

It shows in the field too. Webkit's implementations are often buggy and incomplete, whereas while Trident might not have the broad array of implementations that Webkit does, the standards it does implement are far more refined.

I don't. I'm just tired of hearing Microsoft shills blathering on as if every company and person on the web has some obligation to design everything around their products.

Okay dude, you're just being pathetic now. And I say this as someone that often agrees with you on things such as Windows 8, I think that OS is an abomination.

But this isn't about Microsoft, this is about every other browser that isn't Chrome and making sure everyone (Including the Microsoft I currently dislike) has a fair chance at rendering a page correctly, and not being shut out by a bunch of vendor specific cruft.

IE needs to die completely.. end of..

and, no, IE8, IE9 and IE10 will be the new IE6. Apple and Google along with Mozilla are following W3C and WHATWG in implementing new features and support for CSS3 and HTML and thus when we build web stuff today it just works across all of these browsers with most of the fancy effects and we are still jumping hoops and having to put up with Microsoft's IE crap.

So ironic but expected that Microsoft can't understand why they are terrible in this regard as well. IE 10 is better than all other IEs but it's STILL IE and it's still Microsoft, so we will continue supporting webkit because it evolves and browsers update themselves to be always current on user's machines while Microsoft still peddles their old proprietary crap..

Hey Microsoft, here's an idea for you.. MAKE IE based on webkit and help build a better webkit base since it's open and help developers develop for one HTML/web engine? Oh you don't want to, or you have to deal with your users who you screwed with terrible IEs? Well the web and internet in general won't wait for you. Nobody cares what you think anymore. You have shown us what web looks like with you and it's not a pretty picture and it's so ironic that we are being warned by MS about competing rendering engine not being "good" for us.

Just die already and stop whining since you are a decade late to the next generation.

What are you smoking? Mind to share with us?

Nobody is breaking standards. If anything Webkit implements them first.

Are you just being thick on purpose? Or do you really not understand what this article is all about?

Your blind hate for MS just affects your reading comprehension it seems.

All MS is asking is, don't make the same mistake we did, the web is on the right track, lets all try to be standards compliant.

  • Like 2
Rich coming from someone who is defending a company who killed web progress for a decade with their crap browser and is now criticizing open source webkit that has even better standards support than IE10 as being "proprietary". I guess you have to be special type of blind to miss the irony and hypocrisy in this.. The whole world is laughing at Microsoft. Riiight.. the ONLY proper test is the one sponsored by Microsoft that shows IE10 doing well with HTML5.. GOT IT!

That's your mistake. I'm not defending Microsoft per se, I'm just defending their request which is perfectly sensible. If they were saying that they want developers to use their own proprietary extensions I'd happily argue that that was a ridiculous position. However, all they're doing here is asking developers to use standards.

I'm well aware of Microsoft's history (and the irony of the situation) but you're the one who wants to see a repeat of that situation.

Nobody is breaking standards. If anything Webkit implements them first.

ok, lets break this down to you

Step 1. W3C creates a new spec for touch controls which all browsers can implement as a standardized platform

Step 2. All browsers start implementing it.

Step 3. EXCEPT, Chrome/Webkit since google instead decides to make their own incompatible version who is also inferior in many ways.

Step 4. All browser use the standard version except chrome, and some like Opera try to implement Googles version on top of the actual standard to support both versions despite obvious functionality differences and certain things who can't be supported and translated

You're saying this is good, that this is how it should be, instead of Google just using the actual accepted Standard which is also better ?

Seriously.

FYI this is actually worse than what MS did, as back then there was a serious lack of standards, and most of the new proprietary stuff MS implemented didn't have a standard and didn't exist before. Google on the other hand is purposely breaking a standard.

based on what? From what I see, and numbers say it all, they are following the standards the closest (btw Maxthon is webkit as well). IE10 is dead last.

And stop with this Google is doing this sh**.. Webkit is NOT Google.. Webkit is everyone. IE is Microsoft only.. this alone should make it obvious to you that MS is full of crap.

GG9

Please go away. If I ask you, "can you cook Bibimbap?" and you answer yes, it doesn't mean you can cook it let alone properly. That's what your quoted "test" does. So please, learn about things before talking or you will only embarrass yourself like you are doing now.

...while 99% [marketshare] on mobile makes it a standard...

ok. I should have read this quote before. Then I wouldn't bother replying to a silly kid like you.

-webkit-weed

Figures. I was hoping it'd be weed instead of -webkit-weed.

99% market share means -webkit-weed is the standard, I guess.

Why the **** support any company which wants to make a web developer's life hard?

You mean like Microsoft did for nearly a decade? pot, kettle, black

Peacekeeper is not a valid benchmark. It tests things which are out of spec.

It doesn't account for them in the final score either. Peacekeeper is mainly a performance benchmark and Chrome blows IE apart on that front.

Not as tired as I am of seeing you call everyone who disagrees with you a shill. If you haven't got an argument and need to rely on abuse it would probably be best if you just don't post.

Pretty rich coming from a guy claiming that I "knew nothing" and then when proven to be wrong went off at an alternate tangent rather than admitting so.

It doesn't account for them in the final score either. Peacekeeper is mainly a performance benchmark and Chrome blows IE apart on that front.

Of course it does peacekeeper doesn't test real world situations performance and Chrome is coded specifically to score high on the test,

You mean like Microsoft coded IE9 to cheat Sunspider? I've been using Peacekeeper since it was made available and I have always found it's findings in line with what I actually get out of real world usage.

It's irrelevant? Having everyone access to the engine's base and being able to build upon it, improve it, independent from any one company is irrelevant to you?

Yeah, please. You clearly don't know what you are talking about nor you have an idea of how open source works.

It matters because Microsoft can follow W3C standards now and when it gets 80% of marketshare again they can do the same thing they did with IE6 and nobody can do anything about it. You don't see how that's a possibility?

With webkit that can't happen because it is now owned, nor developed exclusively by a single company. How can you people not get that.

The reason IE is a slower lifecycle is MS supports its corporate apps with such longevity so they can regain their investments. When you spend 10 million dollars to implement a new ERP system, you can give a rats ass about the latest and greatest CSS gimmick, what you want is a browser that works and the best thing to make sure that it works and is supported perpetually is that it adheres to the standards approved by the standardization body. Being able to modify the engine/change things and hack for the sake of hacking does NOTHING to improve the industry, in fact it greatly detracts from the ability to build manageable apps.

also, you seem to like the sound of your own voice. Maybe if you scream it enough people will believe it? lol

You mean like Microsoft did for nearly a decade? pot, kettle, black

If Microsoft were trying to act like they're the saviours of web standards you'd maybe have a point. But since all they're doing is trying to influence developers to write standards-compliant code that benefits everyone, rather than proprietary Webkit-specific code that only benefits Apple and Google, you have no point.

And on top of that, you're really starting to look petty. Microsoft may be retarded, but they're not always wrong.

Pretty rich coming from a guy claiming that I "knew nothing" and then when proven to be wrong went off at an alternate tangent rather than admitting so.

You don't know what you're talking about which is why you have to rely on insults. You constantly undermine your own arguments with your nonsensical personal attacks and it's not worth discussing anything with you if you can't post sensible comments.

  • Like 2

Ignorant IE Hating. Internet Explorer is in the right here and is following the spec. You harp on and on about spec compliance, yet when it comes to this it doesn't matter? This is not a deficiency in IE that Microsoft is asking people to fix. This is IE following the spec to the letter and people not using proper code. Since people are never going to get their heads out of there asses, IE should just start parsing -webkit prefixed CSS like opera. Then we can all pretend we're webkit just like we all pretend we're netscape.

http://webaim.org/bl...string-history/

Market share means nothing (or should anyways).

Vendor specific prefixes are a bad a idea and were a bad idea and now we're seeing the result of it. Vendor specific prefixes should have never been implemented in any version of the browser designed for the average user. It causes this horrible mess of a situation.

  • Like 2

based on what? From what I see, and numbers say it all, they are following the standards the closest (btw Maxthon is webkit as well). IE10 is dead last.

GG9

Sorry to quote this again but I had to point out this example of 448 score chrome fail: http://newilk.com/te...eholder_styling

If this is not enough to shut you up, you either have logic issues or are one of the best example of fanboi.

PS: Assuming I'm not wrong, this is the specific relevant test in html5test.com : http://html5test.com/compare/feature/form-other-placeholder.html

As you can see, most browsers get full points in this test while only IE10 and Firefox support it (almost) properly.

Out of your 448 point chrome (or webkit), there is huge percentage of points awarded for saying "yes, I can cook 5-star Bibimbap" while what it cooks may be worse than eating trash from garbage dump.

So for the last time, do not quote html5test again. It is a great site for a quick overview. But it is not solid, often misleading and tests **** loads of things that are not part of HTML5 or not even standards.

By the way, Chrome is a great browser. So is IE10 and Firefox. I personally do not like firefox except firebug (<3).

I find this entire thread hilarious.

I don't think anyone on this site will agree that IE6 was the most awesome browser of all time. Hell I was using FireFox to escape it back when I was on XP. Microsoft even want it to die for Christ's sake, and that's saying something.

So long story short, IE6 shall be regarded as the dark ages of the internet from which FF and Opera inspired a renaissance.

Then we got IE7. At first I ignored it and carried on using FF in Vista, until I had to do a reinstall and didn't bother using it and carried on used IE7 as it had tabbed browsing and well, worked. Still wasn't perfect but was a step in the right direction at least for Microsoft standards wise can we not all agree?

Next up IE8. Does anyone remember using the IE8 beta's and watching all the sites fall over unless it was in compatibility mode? Again was Microsoft not trying to make a better standards compatible browser? Still wasn't quite there though was it, and performance needed a swift kick in the arse, again I think we can all agree on that?

Close, but no cigar.

Then we had IE9 that showed the world that Microsoft was serious about the web again. Supporting part of HTML5 and CSS3 with a great performance boost as well. And now, a year and half later we now have IE10. If anything I think everyone should be supporting Microsoft's catch up over the past few years.

But the best thing I find hilarious is the bashing that IE isn't HTML5 standard compatible? Hate to point this out, bit of a small detail but HTML5 ISN'T A FREAKING RATIFIED STANDARD YET! Once W3C has ratified it and said "Hey everyone, this is what you should be doing" and IE(insert version number at the time) isn't standards compatible, then yes go ahead, bash away.

No really I won't stop you, hell I'll join in with you. Microsoft have time to do it, they have till 2014 till the recommendation is out so they don't have an excuse. I don't think you'll find many people defending them for being late.

Hell I think we should start making bets when the IE11 preview will come out. I give it 1 month after IE10 for Win7 comes out.

IE across the board sucks and from IE6 to IE9 has broken the web over and over again.. and then Microsoft starts coming out and complaining how everyone is using webkit (an open source browser engine that is absolutely KICK ASS) and because they are adding new features (who btw, will most likely be adopted by WHATWG and W3C eventually).

Wtf are we talking about.. and yes.. IE 10 sucks compared to every other browser. Just because it's a bit more compliant with HTML5 as a standard still doesn't make it great.. it makes it suck less.

IE across the board sucks and from IE6 to IE9 has broken the web over and over again.. and then Microsoft starts coming out and complaining how everyone is using webkit (an open source browser engine that is absolutely KICK ASS) and because they are adding new features (who btw, will most likely be adopted by WHATWG and W3C eventually).

Wtf are we talking about.. and yes.. IE 10 sucks compared to every other browser. Just because it's a bit more compliant with HTML5 as a standard still doesn't make it great.. it makes it suck less.

I see you're ignoring all the posts you can't refute and argue with again, and just sprouting bull crap about how awesome Google and Webkit is again.

*yawn*

  • Like 2

I see you're ignoring all the posts you can't refute and argue with again, and just sprouting bull crap about how awesome Google and Webkit is again.

*yawn*

You and others didn't refute anything but just whine and defend garbage that Microsoft is and was in regards to IE browsers. The reason web is still having trouble moving forward is Microsoft and IE and nobody else. But that goes over your head.

The point of Microsoft whining is not about HTML5 and standards.. it's about them losing dominance and being completely irrelevant on mobile. And that's completely their fault and is completely disingenuous (but what else do you expect form that company who gave us IE6) to come out and whine how open source engines are introducing new features that IE can't support. Hey, guess what, the world doesn't care about Microsoft anymore. The world has moved on. We build stuff for webkit, gecko because stuff just works and for the past years we got stuck with IE garbage and having to write hacks and tons of other crap because of Microsoft (and not just IE6.. IE7, IE8, IE9.. they ALL suck). The web would be a better place without them. And nobody cares about IE10. Because Microsoft is unreliable Today it might be somewhat following HTML5 standard, but tomorrow Microsoft will bring more of the proprietary extensions (that are already happening btw with WinRT) and they will break everything again so they can try to hijack the web again towards their own interests.

So they are a joke of the developer world. Every serious web developer LOATHES Microsoft and IE.. and laughs their ass off at Microsoft telling anyone anything about compatibility and standards, especially comparing open source engines and others to their proprietary IE6. The biggest irony of all.

Again, the standards organizations MADE a standard for touch controls that all browsers decided to follow. Google decided to make their own incompatible and non compliant and in fact a worse implementation. of touch controls and not implement the standard one.

you keep ignoring this little fact, the standard already existed, Google's method isn't going to be a standard, they already had a standard, a better standard.

And we're not defending MS, we're arguing to Google shouldn't make their own standards when there are already standards for it.

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

    • No registered users viewing this page.
  • Posts

    • The Light of Life? We actually do glow till our Death, study finds by Sayan Sen Image by Rafael Rendon via Pexels A study by researchers at the University of Calgary has found that living organisms produce an extremely faint light known as ultraweak photon emission, and that this glow appears to drop significantly after death. The research was published in the Journal of Physical Chemistry in April 2025 and quickly drew widespread attention, leading to more than 200 news stories about the findings. Ultraweak photon emission (or UPE), sometimes called biophoton emission, refers to tiny amounts of light released by living cells as a result of normal biological activity. A photon is the basic particle of light, and researchers say every living system examined so far, including plants and animals, has been found to emit these photons. The glow is far too faint to be seen by the human eye. “I suppose it has a little to do with people being reminded of auras,” says Dr. Christoph Simon, PhD, one of the authors of the study and a professor in the Department of Physics and Astronomy in the Faculty of Science. “It is a fact that living beings glow. It’s a very weak glow, but it’s there and visible with very sensitive cameras.” According to the study, the light involved is extremely weak, ranging from 10 to 1,000 photons per square centimetre per second across a spectral range of 200 to 1,000 nanometres. For comparison, a nanometre is one-billionth of a metre and is commonly used to measure wavelengths of light. Detecting emissions at such low levels requires highly specialized equipment. To study the phenomenon, researchers used electron-multiplying charge-coupled device (EMCCD) and charge-coupled device (CCD) cameras. These imaging systems are designed to detect extremely small amounts of light, including individual photons, while minimizing background noise. The technology allowed researchers to capture signals that would otherwise be impossible to observe. The team worked with the Human Health Therapeutics Research Centre at the National Research Council of Canada (NRC) in Ottawa to examine photon emissions in mice. Researchers took two-hour exposure images of the animals before and after death and compared the results. “We saw that the level of light that they emit – this biophoton glow – is distinctly different between living and dead animals,” says Dr. Daniel Oblak, PhD, an associate professor in Physics and Astronomy and the corresponding author of the study. The images showed a clear decrease in photon emissions after death across the entire body of each mouse. According to the researchers, this provided direct evidence that living and dead tissue produce different levels of ultraweak photon emission. “It’s a very small amount and it’s, of course, very tricky to detect,” Oblak says. The study grew out of discussions between Simon, whose research interests include quantum biology, and Oblak, whose work focuses on detecting light for quantum communication experiments. Quantum biology is a field that explores whether processes described by quantum physics, which studies matter and energy at very small scales, may also play a role in living systems. “Since I work as a quantum physicist on light detection for quantum communication, I thought that experimentally we have a lot of the tools to be able to detect the light,” Oblak explains. The researchers also investigated UPE in plants and found that the light changed in response to stress. When plants were exposed to higher temperatures or physically injured, their photon emissions increased. Chemical treatments also affected the glow. Among the substances tested, the local anesthetic benzocaine produced the strongest emission response when applied to injured plant tissue. These findings suggest that ultraweak photon emission is closely linked to biochemical and metabolic activity inside living organisms. Metabolism refers to the chemical reactions that allow cells and organisms to stay alive and function. Because these reactions change when an organism experiences stress, injury or disease, researchers believe UPE may provide a way to monitor those changes. The researchers stress that the glow is a physical and biological phenomenon, not a metaphysical one. Oblak says more research is needed to understand exactly how the light is produced and what information it may reveal about the condition of living tissue. “We must understand what that is to figure out what’s happening,” he says. “If we can understand how that relates to certain influences on the body – stress, diseases – then that could be used as a diagnostic tool.” The researchers believe the technique could eventually help scientists study health and disease without invasive procedures. Because UPE can be measured without adding dyes, markers or labels, it may offer a way to monitor whether tissue is healthy, damaged or alive. In plants, it could help researchers better understand how organisms respond to injury, heat and other forms of stress. While the work is still in its early stages, the study demonstrates that ultraweak photon emission imaging can provide a non-invasive and label-free way to observe biological activity. Researchers say the approach could become a useful tool for studying vitality, stress responses and other important processes in both animals and plants. Source: University of Calgary, ACS publication This article was generated with some help from AI and reviewed by an editor. Under Section 107 of the Copyright Act 1976, this material is used for the purpose of news reporting. Fair use is a use permitted by copyright statute that might otherwise be infringing.
    • Damn, I loved this show back in the day.  
    • Rufus 4.15.2393 Beta 2 by Razvan Serea Rufus is a small utility that helps format and create bootable USB flash drives, such as USB keys/pendrives, memory sticks, etc. Despite its small size, Rufus provides everything you need! Oh, and Rufus is fast. For instance it's about twice as fast as UNetbootin, Universal USB Installer or Windows 7 USB download tool, on the creation of a Windows 7 USB installation drive from an ISO (with honorable mention to WiNToBootic for managing to keep up). It is also marginally faster on the creation of Linux bootable USBs from ISOs. A non-exhaustive list of Rufus supported ISOs is available here. It can be especially useful for cases where: you need to create USB installation media from bootable ISOs (Windows, Linux, UEFI, etc.) you need to work on a system that doesn't have an OS installed you need to flash a BIOS or other firmware from DOS you want to run a low-level utility Rufus 4.15.2393 Beta 2 changelog: Add RISC-V 64 support to UEFI:NTFS Improve the guards for using the "silent" option Improve the ability to cancel during write retries Improve progress reporting for compressed image extraction Fix unrestricted XML entity expansion and integer overflow in ezxml parser (courtesy of @esadowski4) [GHSA-55r2-34wg-8mv9] Fix "silent" Windows installation failing at 75% in most cases [#2960] Fix a crash during boot when using UEFI:NTFS on Snapdragon X based ARM64 platforms [#2934] Fix the first WUE option always being checked by default [#2965] Fix an infinite loop when using Windows ISOs that contain multiple WIMs Fix "Enable runtime UEFI media validation" checkbox not always being properly enabled Other WUE improvements/fixes for OneDrive removal and username validation (with thanks to @christian8641) [#2984, #2991] Download: Rufus 4.15 Beta 2 | 1.9 MB (Open Source) Links: Rufus Home Page | Project Page @GitHub | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Tixati 3.43 by Razvan Serea Tixati is a free and easy to use BitTorrent client featuring detailed views of all seed, peer, and file transfer properties. Also included are powerful bandwidth charting and throttling capabilities, and a full DHT implementation. Tixati is one of the most advanced and flexible BitTorrent clients available. And unlike many other clients, Tixati contains NO SPYWARE, NO ADS, and NO GIMMICKS. Tixati portable version is meant to run on a USB flash drive or other portable media. It stores all its configuration files in the same folder as the executable binary files, and all file paths are stored in a format relative to the program executable folder. It is important you do not delete the "tixati_portable_mode.txt" file within the executables folder. This file is what triggers Tixati to run in portable mode. (The executable binaries are actually the same as the standard edition binaries.) When running the portable edition from a USB flash drive, especially one that is formatted in FAT16/FAT32, you may experience some lag when initially loading a new transfer. This is because initializing and allocating large files on flash-based media consumes a greater amount of time and resources compared to a conventional hard-drive. Tixati has the following features: detailed views of all aspects of the swarm, including peers, pieces, files, and trackers support for magnet links, so no need to download .torrent files if a simple magnet-link is available super-efficient peer choking/unchoking algorithms ensure the fastest downloads peer connection encryption for added security full DHT (Distributed Hash Table) implementation for trackerless torrents, including detailed message traffic graphs and customizable event logging advanced bandwidth charting of overall traffic and per-transfer traffic, with separate classification of protocol and file bytes, and with separate classification of outbound traffic for trading and seeding highly flexible bandwidth throttling, including trading/seeding proportion adjustment and adjustable priority for individual transfers and peers bitfield graphs that show the completeness of all downloaded files, what pieces other peers have available, and the health of the overall swarm customizable event logging for each download, and individual event logs for all peers within the swarm expert local file management functions which allow you to move files to a different partition even while downloading is still in progress 100% compatible with the BitTorrent protocol Windows and Linux-GTK native versions available Tixati 3.43 changelog: Several major DHT improvements Added several screening heuristics to filter malicious DHT nodes, prevent Sybil floods Rewrote DHT search algorithms to add support for multi-path lookups Improved DHT logging, more details in several error messages Extended timeout lengths for outgoing queries over I2P Added incoming query / response per second to DHT table status display Updated Regex engine to PCRE2 Faster Search function, scans channel user profiles in much less time Fixed problems with file name parsing and date handling in RSS Faster and more accurate RSS filtering and episode number detection Several optimizations to global text processing functions, such as UTF-8 cleaning, line splitting, and token parsing Complete update of port-mapping UPNP/NAT-PMP engine, added PCP support, mapping over VPN support, and more Several refinements to default gateway detection on Windows / Android, which is used for port-mapping Support for IPv6 interface-scoped addresses, which is sometimes needed for IPv6 gateway detection and port mapping Full support for PCP port remapping, added backup zero-port query in case requested port is rejected New UPNP/NAT-PMP Monitor in Help > Diagnostics New reflected local port/location tracker that analyzes DHT replies to detect true port/location and NAT mapping type New TCP/UDP Ports monitor in Help > Diagnostics, with several statistic and information tabs, and a detailed event log Calculated/reflected local port is now used for port parameter in tracker queries and peer handshake Fixed several problems with Linux Wayland compatibility Completely replaced tray icon functions in Linux, new SNI implementation is now the default with GSI backup Implemented full DBus-Menu server to be used by new SNI tray icon implementation Replaced Linux tray balloon notification DBus client Rewrote auto-shutdown DBus interface for Linux Rewrote sleep inhibit DBus interface for Linux Dropped deprecated Linux dbus-glib dependencies Completely new Windows asynchronous file handling, now using IOCP model with several block-alignment optimizations Better handling of system network resets and interface down/up cycles Added option to fully clear configuration in Settings > Import/Export Remember last option checkboxes when using Import/Export Fixed minor I2P incoming connection routing problems Much faster I2P vanity host name finder Much faster channel user vanity key finder Raised length limit for torrent tracker remote failure messages to 120 from 64 Fixed problems setting download location on a torrent before the meta info is resolved Added location/MOC paths to category pane tooltips Several minor Web Interface fixes Refinements to static and scrolling ellipsizing layout routines Several fixes and improvements to single and multi-line text edit controls Many other minor fixes throughout the user interface A major overhaul of the Android framework has also been done: API target raised to 35, page alignment set to 16K Rewrote all inset processing routines Full rewrite of foreground service, application, and main activity objects New permission request routines Added multi-cast lock request before UPNP/LPDP discovery operations Fixed file permission and locking problems when loading .torrent from web browsers Fixed problems with Z-ordering of modal / non-modal and popup windows Fixed handling of back gesture on newer OS Added status bar icon adjustment based on status bar background color Added option in Settings > UI > Behavior to continue running in tray when task removed from recents App can be closed by swiping away notification Rewrote IME interface, fixed several problems with auto-correct, on-screen keyboard visibility, and cursor positioning Added full support for Android hardware mouse and keyboard function Added full tooltip implementation for Android hovering via mouse or other cursor device Full rewrite of popup menu widgets to better support hardware pointers and keyboard Added mouse cursor updating framework for Android hovering Added Settings > Import/Export to Android builds Added language file support to Android builds Download: Tixati 64-bit | Tixati 32-bit ~20.0 MB (Freeware) Download: Portable Tixati 3.43 | 114.0 MB Download: Tixati 3.43 for Linux | Android View: Tixati Website | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Firefox 152.0.1 by Razvan Serea Firefox is a fast, full-featured Web browser. It offers great security, privacy, and protection against viruses, spyware, malware, and it can also easily block pop-up windows. The key features that have made Firefox so popular are the simple and effective UI, browser speed and strong security capabilities. Firefox has complete features for browsing the Internet. It is very reliable and flexible due to its implemented security features, along with customization options. Firefox includes pop-up blocking, tab-browsing, integrated Google search, simplified privacy controls, a streamlined browser window that shows you more of the page than any other browser and a number of additional features that work with you to help you get the most out of your time online. Firefox key features Enhanced Tracking Protection (ETP) – Blocks trackers, cookies, cryptominers, and fingerprinters by default. Private Browsing Mode – Deletes history, cookies, and temporary files when closed. Lightweight & Fast Performance – Optimized memory usage with efficient page loading. Cross-Platform Sync – Sync bookmarks, passwords, history, and open tabs across devices. Customizable Interface – Toolbars, themes, and extensions can be tailored to user needs. Strong Privacy Controls – Options to manage cookies, permissions, and site data easily. Reader Mode – Strips away clutter for distraction-free reading. Pocket Integration – Save and read articles offline with Pocket built into Firefox. Picture-in-Picture (PiP) – Watch videos in a floating window while multitasking. Extensions & Add-ons – Vast library for productivity, security, and personalization. Built-in PDF Viewer – No need for external software to view PDFs. Firefox Monitor – Alerts users if their email is part of a known data breach. Multi-Account Containers – Isolate browsing sessions (e.g., work, personal, shopping). Performance & Resource Efficiency – Uses fewer system resources than some competitors. Open Source & Community-Driven – Transparent development with global contributions. Firefox 152.0.1 fixes: Fixed frequent crashes affecting users with Intel Raptor Lake processors. (Bug 2039575) Fixed an issue on macOS where choosing a PDF option, such as "Save as PDF", from the system print dialog would send the job to your printer instead of saving a file. (Bug 2047850) Download: Firefox 64-bit | Firefox 32-bit | ARM64 | ~70.0 MB (Freeware) Download: Firefox for MacOS | 146.0 MB View: Firefox Home Page | Release Notes Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • One Year In
      hhgygy earned a badge
      One Year In
    • One Month Later
      AMV earned a badge
      One Month Later
    • Week One Done
      AMV earned a badge
      Week One Done
    • Collaborator
      ryansurfer98 went up a rank
      Collaborator
    • One Month Later
      Eurosoft10 earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      514
    2. 2
      +Edouard
      169
    3. 3
      PsYcHoKiLLa
      78
    4. 4
      Steven P.
      73
    5. 5
      Michael Scrip
      71
  • Tell a friend

    Love Neowin? Tell a friend!