If you use the Chrome dev tools you can watch the network messages getting sent when you save your emblem and you'll see that it's just sending enough information to repopulate the emblem editor as well as base64 encoded renderings of the emblems at different resolutions (for different parts of the website.) You can even make it so that different sizes of your emblem use different images, etc.
Originally Posted by chuyskywalker
Here's the quick jist of it: You have to hijack the http connection, modify a JS file so that when it uploads it pushes your image code instead of what the canvas element renders.
you can upload your own image in the form of base64 encoded image rather than using the emblem editor on the webbrowser.
I found out that it maybe the file called "bundle_base_index_#######.js" is responsible for updating the server on the changes you made on the emblem editor.
The ##### is just a bunch of unique numbers i think.
the question is what do you modify and how do you get the website to use it? do i modify the js file in the cookies or the cache and the website automatically uses the js file? can anyone please figure it out and explain? thanks in advance.