Timeline for Can we support internal "chrome://" URLs?
Current License: CC BY-SA 3.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 20, 2017 at 10:32 | history | edited | CommunityBot |
replaced http://meta.stackexchange.com/ with https://meta.stackexchange.com/
|
|
| Apr 23, 2014 at 13:35 | history | edited | CommunityBot |
Fixup of bad MSO links to MSE links migration
|
|
| Apr 23, 2014 at 9:11 | history | edited | CommunityBot |
Migration of MSO links to MSE links
|
|
| Jul 8, 2012 at 2:44 | vote | accept | CommunityBot | ||
| Jul 8, 2012 at 2:44 | vote | accept | CommunityBot | ||
| Jul 8, 2012 at 2:44 | |||||
| Jul 8, 2012 at 2:44 | comment | added | user137430 | Okay, thanks for answering a duplicate. =P I just couldn't find it via SE or Google. | |
| Jul 8, 2012 at 2:43 | comment | added | random Mod | That's the security concern. Google Chrome won't let you get yourself in trouble by clicking on such links where it hasn't generated them itself | |
| Jul 8, 2012 at 2:41 | vote | accept | CommunityBot | ||
| Jul 8, 2012 at 2:41 | |||||
| Jul 8, 2012 at 2:41 | comment | added | user137430 |
Ah. So the reason is that Google Chrome actually doesn't follow chrome:// links?
|
|
| Jul 8, 2012 at 2:37 | comment | added | random Mod | Create an HTML page on your machine with such a link. And then try and click on it. See where it takes you. | |
| Jul 8, 2012 at 2:32 | comment | added | user137430 | I'm reading that other post (thanks for finding it, search on SE sucks =/), but what was Code Grey's security concerns? | |
| Jul 8, 2012 at 2:30 | history | answered | randomMod | CC BY-SA 3.0 |