google docs iframe - change padding

Multi tool use
Multi tool use












8















I have an embedded iframe that has been created publishing a google doc.
The iframe automatically applies a large padding to its body resulting in the text being a very narrow and ugly column. I have to change that.



I have tried to create a custom directive:



app.directive('iframeWithStyle', [function(){
return {
restrict: 'A',
link: function(scope, element, attrs){
element.on('load', function(){
var iframe = element[0];
var grabbedElement = iframe.querySelector("body");
// -> grabbedElement is null here
});
}
}}]);


which is applied to:



<iframe iframe-with-style
src="https://docs.google.com/document/d/somethingABC123/pub?embedded=true">
</iframe>


but iframe.querySelector returns null and iframe.contentWindow.document results, as expected, in




Uncaught DOMException: Blocked a frame with origin
"http://localhost:8100" from accessing a cross-origin frame.




I have looked at a workaround but I have a feeling that it's overkill (ex: safe cross-communication with messages).



I tried to fight the padding with some css applied to what I can reach.
For example:



iframe {
padding: 0px !important;
margin-left: -50px;
margin-right: 50px;
}


css applied to the body of the iframe seems to be simply ignored.



Once upon a time there were some convenience attributes, such as marginwidth. Tried that too.
I was also wondering if google does not offer some "sugar" but googling around did not help.



Note: it really does not have to be an iframe, but I need to show that formatted gdoc within the app in a way that it is readable; and for that I need to reduce that padding.





Adding a plunker: https://plnkr.co/edit/XIkgPe7ecLyFfhq1Q3Sv?p=preview










share|improve this question

























  • Add html element code to which you are applying the Directive

    – Mr_Perfect
    Jun 13 '17 at 10:40











  • I have added the html code to which I am applying the directive.

    – NoIdeaHowToFixThis
    Jun 13 '17 at 10:45











  • Once look into this stackoverflow.com/questions/1451208/…

    – SaiUnique
    Jun 13 '17 at 10:58






  • 1





    Thanks @SaiUnique, but the iframe is served from google. That's the problem.

    – NoIdeaHowToFixThis
    Jun 13 '17 at 11:02






  • 1





    I think it's better to have a parent element to styles the iframe. just style the parent instead of iframe

    – Mr_Perfect
    Jun 13 '17 at 11:10


















8















I have an embedded iframe that has been created publishing a google doc.
The iframe automatically applies a large padding to its body resulting in the text being a very narrow and ugly column. I have to change that.



I have tried to create a custom directive:



app.directive('iframeWithStyle', [function(){
return {
restrict: 'A',
link: function(scope, element, attrs){
element.on('load', function(){
var iframe = element[0];
var grabbedElement = iframe.querySelector("body");
// -> grabbedElement is null here
});
}
}}]);


which is applied to:



<iframe iframe-with-style
src="https://docs.google.com/document/d/somethingABC123/pub?embedded=true">
</iframe>


but iframe.querySelector returns null and iframe.contentWindow.document results, as expected, in




Uncaught DOMException: Blocked a frame with origin
"http://localhost:8100" from accessing a cross-origin frame.




I have looked at a workaround but I have a feeling that it's overkill (ex: safe cross-communication with messages).



I tried to fight the padding with some css applied to what I can reach.
For example:



iframe {
padding: 0px !important;
margin-left: -50px;
margin-right: 50px;
}


css applied to the body of the iframe seems to be simply ignored.



Once upon a time there were some convenience attributes, such as marginwidth. Tried that too.
I was also wondering if google does not offer some "sugar" but googling around did not help.



Note: it really does not have to be an iframe, but I need to show that formatted gdoc within the app in a way that it is readable; and for that I need to reduce that padding.





Adding a plunker: https://plnkr.co/edit/XIkgPe7ecLyFfhq1Q3Sv?p=preview










share|improve this question

























  • Add html element code to which you are applying the Directive

    – Mr_Perfect
    Jun 13 '17 at 10:40











  • I have added the html code to which I am applying the directive.

    – NoIdeaHowToFixThis
    Jun 13 '17 at 10:45











  • Once look into this stackoverflow.com/questions/1451208/…

    – SaiUnique
    Jun 13 '17 at 10:58






  • 1





    Thanks @SaiUnique, but the iframe is served from google. That's the problem.

    – NoIdeaHowToFixThis
    Jun 13 '17 at 11:02






  • 1





    I think it's better to have a parent element to styles the iframe. just style the parent instead of iframe

    – Mr_Perfect
    Jun 13 '17 at 11:10
















8












8








8








I have an embedded iframe that has been created publishing a google doc.
The iframe automatically applies a large padding to its body resulting in the text being a very narrow and ugly column. I have to change that.



I have tried to create a custom directive:



app.directive('iframeWithStyle', [function(){
return {
restrict: 'A',
link: function(scope, element, attrs){
element.on('load', function(){
var iframe = element[0];
var grabbedElement = iframe.querySelector("body");
// -> grabbedElement is null here
});
}
}}]);


which is applied to:



<iframe iframe-with-style
src="https://docs.google.com/document/d/somethingABC123/pub?embedded=true">
</iframe>


but iframe.querySelector returns null and iframe.contentWindow.document results, as expected, in




Uncaught DOMException: Blocked a frame with origin
"http://localhost:8100" from accessing a cross-origin frame.




I have looked at a workaround but I have a feeling that it's overkill (ex: safe cross-communication with messages).



I tried to fight the padding with some css applied to what I can reach.
For example:



iframe {
padding: 0px !important;
margin-left: -50px;
margin-right: 50px;
}


css applied to the body of the iframe seems to be simply ignored.



Once upon a time there were some convenience attributes, such as marginwidth. Tried that too.
I was also wondering if google does not offer some "sugar" but googling around did not help.



Note: it really does not have to be an iframe, but I need to show that formatted gdoc within the app in a way that it is readable; and for that I need to reduce that padding.





Adding a plunker: https://plnkr.co/edit/XIkgPe7ecLyFfhq1Q3Sv?p=preview










share|improve this question
















I have an embedded iframe that has been created publishing a google doc.
The iframe automatically applies a large padding to its body resulting in the text being a very narrow and ugly column. I have to change that.



I have tried to create a custom directive:



app.directive('iframeWithStyle', [function(){
return {
restrict: 'A',
link: function(scope, element, attrs){
element.on('load', function(){
var iframe = element[0];
var grabbedElement = iframe.querySelector("body");
// -> grabbedElement is null here
});
}
}}]);


which is applied to:



<iframe iframe-with-style
src="https://docs.google.com/document/d/somethingABC123/pub?embedded=true">
</iframe>


but iframe.querySelector returns null and iframe.contentWindow.document results, as expected, in




Uncaught DOMException: Blocked a frame with origin
"http://localhost:8100" from accessing a cross-origin frame.




I have looked at a workaround but I have a feeling that it's overkill (ex: safe cross-communication with messages).



I tried to fight the padding with some css applied to what I can reach.
For example:



iframe {
padding: 0px !important;
margin-left: -50px;
margin-right: 50px;
}


css applied to the body of the iframe seems to be simply ignored.



Once upon a time there were some convenience attributes, such as marginwidth. Tried that too.
I was also wondering if google does not offer some "sugar" but googling around did not help.



Note: it really does not have to be an iframe, but I need to show that formatted gdoc within the app in a way that it is readable; and for that I need to reduce that padding.





Adding a plunker: https://plnkr.co/edit/XIkgPe7ecLyFfhq1Q3Sv?p=preview







angularjs iframe google-docs






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jun 13 '17 at 11:52







NoIdeaHowToFixThis

















asked Jun 13 '17 at 10:22









NoIdeaHowToFixThisNoIdeaHowToFixThis

1,63921639




1,63921639













  • Add html element code to which you are applying the Directive

    – Mr_Perfect
    Jun 13 '17 at 10:40











  • I have added the html code to which I am applying the directive.

    – NoIdeaHowToFixThis
    Jun 13 '17 at 10:45











  • Once look into this stackoverflow.com/questions/1451208/…

    – SaiUnique
    Jun 13 '17 at 10:58






  • 1





    Thanks @SaiUnique, but the iframe is served from google. That's the problem.

    – NoIdeaHowToFixThis
    Jun 13 '17 at 11:02






  • 1





    I think it's better to have a parent element to styles the iframe. just style the parent instead of iframe

    – Mr_Perfect
    Jun 13 '17 at 11:10





















  • Add html element code to which you are applying the Directive

    – Mr_Perfect
    Jun 13 '17 at 10:40











  • I have added the html code to which I am applying the directive.

    – NoIdeaHowToFixThis
    Jun 13 '17 at 10:45











  • Once look into this stackoverflow.com/questions/1451208/…

    – SaiUnique
    Jun 13 '17 at 10:58






  • 1





    Thanks @SaiUnique, but the iframe is served from google. That's the problem.

    – NoIdeaHowToFixThis
    Jun 13 '17 at 11:02






  • 1





    I think it's better to have a parent element to styles the iframe. just style the parent instead of iframe

    – Mr_Perfect
    Jun 13 '17 at 11:10



















Add html element code to which you are applying the Directive

– Mr_Perfect
Jun 13 '17 at 10:40





Add html element code to which you are applying the Directive

– Mr_Perfect
Jun 13 '17 at 10:40













I have added the html code to which I am applying the directive.

– NoIdeaHowToFixThis
Jun 13 '17 at 10:45





I have added the html code to which I am applying the directive.

– NoIdeaHowToFixThis
Jun 13 '17 at 10:45













Once look into this stackoverflow.com/questions/1451208/…

– SaiUnique
Jun 13 '17 at 10:58





Once look into this stackoverflow.com/questions/1451208/…

– SaiUnique
Jun 13 '17 at 10:58




1




1





Thanks @SaiUnique, but the iframe is served from google. That's the problem.

– NoIdeaHowToFixThis
Jun 13 '17 at 11:02





Thanks @SaiUnique, but the iframe is served from google. That's the problem.

– NoIdeaHowToFixThis
Jun 13 '17 at 11:02




1




1





I think it's better to have a parent element to styles the iframe. just style the parent instead of iframe

– Mr_Perfect
Jun 13 '17 at 11:10







I think it's better to have a parent element to styles the iframe. just style the parent instead of iframe

– Mr_Perfect
Jun 13 '17 at 11:10














2 Answers
2






active

oldest

votes


















5





+100









Change the last portion of your url from true to false.




https://docs.google.com/document/d/1s2nOQZ39dKD-hsmox5twmmKKkuXzOopT1eXFbMh5DeE/pub?embedded=false




The demo includes use of all of the embedded elements:



<iframe>, <embed>, and <object>



Plunker



When you set embedded=true Google server will add a class named .c1 to the <body> of the content inside the <iframe>




.c1 {
background-color: rgb(255, 255, 255);
max-width: 468pt;
padding: 72pt 72pt 72pt 72pt;
}



That's just plain reckless of Google if you ask me. I suggest that you set padding on the content itself and set embedded=false.






share|improve this answer


























  • This is a step forward. Thanks! However, there's a "Published by Google Drive ... " box that gets added once setting `embedded=false", in all the scenarios <iframe>, <embed>, and <object> in your plunker.

    – NoIdeaHowToFixThis
    Jun 15 '17 at 15:55











  • @NoIdeaHowToFixThis You're not the only one that doesn't appreciate Google's heavy handed styling of published documents. Here's something that'll help: gdoc.pub

    – zer00ne
    Jun 16 '17 at 22:31











  • Thank you @zer00ne -gdoc.pub is open source. I will have a look at the repo to understand how they ultimately did the trick.

    – NoIdeaHowToFixThis
    Jun 21 '17 at 9:31











  • You are very welcome @NoIdeaHowToFixThis Until you figure out gdoc.pub, you can try adding padding or margins to the document itself. Not the greatest of choices but that's the double edged sword of Google services: free but spotty control, plus documentation is never complete because they change things often.

    – zer00ne
    Jun 21 '17 at 9:53



















0














There's no need to use an iframe. You can send a CORS request to GET your document in javascript using a regular XMLHttpRequest. The response is an html document which you can read, modify or render.



See this answer for some example code: https://stackoverflow.com/a/53965010/8932511






share|improve this answer























    Your Answer






    StackExchange.ifUsing("editor", function () {
    StackExchange.using("externalEditor", function () {
    StackExchange.using("snippets", function () {
    StackExchange.snippets.init();
    });
    });
    }, "code-snippets");

    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "1"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f44518769%2fgoogle-docs-iframe-change-padding%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    2 Answers
    2






    active

    oldest

    votes








    2 Answers
    2






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    5





    +100









    Change the last portion of your url from true to false.




    https://docs.google.com/document/d/1s2nOQZ39dKD-hsmox5twmmKKkuXzOopT1eXFbMh5DeE/pub?embedded=false




    The demo includes use of all of the embedded elements:



    <iframe>, <embed>, and <object>



    Plunker



    When you set embedded=true Google server will add a class named .c1 to the <body> of the content inside the <iframe>




    .c1 {
    background-color: rgb(255, 255, 255);
    max-width: 468pt;
    padding: 72pt 72pt 72pt 72pt;
    }



    That's just plain reckless of Google if you ask me. I suggest that you set padding on the content itself and set embedded=false.






    share|improve this answer


























    • This is a step forward. Thanks! However, there's a "Published by Google Drive ... " box that gets added once setting `embedded=false", in all the scenarios <iframe>, <embed>, and <object> in your plunker.

      – NoIdeaHowToFixThis
      Jun 15 '17 at 15:55











    • @NoIdeaHowToFixThis You're not the only one that doesn't appreciate Google's heavy handed styling of published documents. Here's something that'll help: gdoc.pub

      – zer00ne
      Jun 16 '17 at 22:31











    • Thank you @zer00ne -gdoc.pub is open source. I will have a look at the repo to understand how they ultimately did the trick.

      – NoIdeaHowToFixThis
      Jun 21 '17 at 9:31











    • You are very welcome @NoIdeaHowToFixThis Until you figure out gdoc.pub, you can try adding padding or margins to the document itself. Not the greatest of choices but that's the double edged sword of Google services: free but spotty control, plus documentation is never complete because they change things often.

      – zer00ne
      Jun 21 '17 at 9:53
















    5





    +100









    Change the last portion of your url from true to false.




    https://docs.google.com/document/d/1s2nOQZ39dKD-hsmox5twmmKKkuXzOopT1eXFbMh5DeE/pub?embedded=false




    The demo includes use of all of the embedded elements:



    <iframe>, <embed>, and <object>



    Plunker



    When you set embedded=true Google server will add a class named .c1 to the <body> of the content inside the <iframe>




    .c1 {
    background-color: rgb(255, 255, 255);
    max-width: 468pt;
    padding: 72pt 72pt 72pt 72pt;
    }



    That's just plain reckless of Google if you ask me. I suggest that you set padding on the content itself and set embedded=false.






    share|improve this answer


























    • This is a step forward. Thanks! However, there's a "Published by Google Drive ... " box that gets added once setting `embedded=false", in all the scenarios <iframe>, <embed>, and <object> in your plunker.

      – NoIdeaHowToFixThis
      Jun 15 '17 at 15:55











    • @NoIdeaHowToFixThis You're not the only one that doesn't appreciate Google's heavy handed styling of published documents. Here's something that'll help: gdoc.pub

      – zer00ne
      Jun 16 '17 at 22:31











    • Thank you @zer00ne -gdoc.pub is open source. I will have a look at the repo to understand how they ultimately did the trick.

      – NoIdeaHowToFixThis
      Jun 21 '17 at 9:31











    • You are very welcome @NoIdeaHowToFixThis Until you figure out gdoc.pub, you can try adding padding or margins to the document itself. Not the greatest of choices but that's the double edged sword of Google services: free but spotty control, plus documentation is never complete because they change things often.

      – zer00ne
      Jun 21 '17 at 9:53














    5





    +100







    5





    +100



    5




    +100





    Change the last portion of your url from true to false.




    https://docs.google.com/document/d/1s2nOQZ39dKD-hsmox5twmmKKkuXzOopT1eXFbMh5DeE/pub?embedded=false




    The demo includes use of all of the embedded elements:



    <iframe>, <embed>, and <object>



    Plunker



    When you set embedded=true Google server will add a class named .c1 to the <body> of the content inside the <iframe>




    .c1 {
    background-color: rgb(255, 255, 255);
    max-width: 468pt;
    padding: 72pt 72pt 72pt 72pt;
    }



    That's just plain reckless of Google if you ask me. I suggest that you set padding on the content itself and set embedded=false.






    share|improve this answer















    Change the last portion of your url from true to false.




    https://docs.google.com/document/d/1s2nOQZ39dKD-hsmox5twmmKKkuXzOopT1eXFbMh5DeE/pub?embedded=false




    The demo includes use of all of the embedded elements:



    <iframe>, <embed>, and <object>



    Plunker



    When you set embedded=true Google server will add a class named .c1 to the <body> of the content inside the <iframe>




    .c1 {
    background-color: rgb(255, 255, 255);
    max-width: 468pt;
    padding: 72pt 72pt 72pt 72pt;
    }



    That's just plain reckless of Google if you ask me. I suggest that you set padding on the content itself and set embedded=false.







    share|improve this answer














    share|improve this answer



    share|improve this answer








    edited Jun 15 '17 at 14:49

























    answered Jun 15 '17 at 14:21









    zer00nezer00ne

    23.5k32242




    23.5k32242













    • This is a step forward. Thanks! However, there's a "Published by Google Drive ... " box that gets added once setting `embedded=false", in all the scenarios <iframe>, <embed>, and <object> in your plunker.

      – NoIdeaHowToFixThis
      Jun 15 '17 at 15:55











    • @NoIdeaHowToFixThis You're not the only one that doesn't appreciate Google's heavy handed styling of published documents. Here's something that'll help: gdoc.pub

      – zer00ne
      Jun 16 '17 at 22:31











    • Thank you @zer00ne -gdoc.pub is open source. I will have a look at the repo to understand how they ultimately did the trick.

      – NoIdeaHowToFixThis
      Jun 21 '17 at 9:31











    • You are very welcome @NoIdeaHowToFixThis Until you figure out gdoc.pub, you can try adding padding or margins to the document itself. Not the greatest of choices but that's the double edged sword of Google services: free but spotty control, plus documentation is never complete because they change things often.

      – zer00ne
      Jun 21 '17 at 9:53



















    • This is a step forward. Thanks! However, there's a "Published by Google Drive ... " box that gets added once setting `embedded=false", in all the scenarios <iframe>, <embed>, and <object> in your plunker.

      – NoIdeaHowToFixThis
      Jun 15 '17 at 15:55











    • @NoIdeaHowToFixThis You're not the only one that doesn't appreciate Google's heavy handed styling of published documents. Here's something that'll help: gdoc.pub

      – zer00ne
      Jun 16 '17 at 22:31











    • Thank you @zer00ne -gdoc.pub is open source. I will have a look at the repo to understand how they ultimately did the trick.

      – NoIdeaHowToFixThis
      Jun 21 '17 at 9:31











    • You are very welcome @NoIdeaHowToFixThis Until you figure out gdoc.pub, you can try adding padding or margins to the document itself. Not the greatest of choices but that's the double edged sword of Google services: free but spotty control, plus documentation is never complete because they change things often.

      – zer00ne
      Jun 21 '17 at 9:53

















    This is a step forward. Thanks! However, there's a "Published by Google Drive ... " box that gets added once setting `embedded=false", in all the scenarios <iframe>, <embed>, and <object> in your plunker.

    – NoIdeaHowToFixThis
    Jun 15 '17 at 15:55





    This is a step forward. Thanks! However, there's a "Published by Google Drive ... " box that gets added once setting `embedded=false", in all the scenarios <iframe>, <embed>, and <object> in your plunker.

    – NoIdeaHowToFixThis
    Jun 15 '17 at 15:55













    @NoIdeaHowToFixThis You're not the only one that doesn't appreciate Google's heavy handed styling of published documents. Here's something that'll help: gdoc.pub

    – zer00ne
    Jun 16 '17 at 22:31





    @NoIdeaHowToFixThis You're not the only one that doesn't appreciate Google's heavy handed styling of published documents. Here's something that'll help: gdoc.pub

    – zer00ne
    Jun 16 '17 at 22:31













    Thank you @zer00ne -gdoc.pub is open source. I will have a look at the repo to understand how they ultimately did the trick.

    – NoIdeaHowToFixThis
    Jun 21 '17 at 9:31





    Thank you @zer00ne -gdoc.pub is open source. I will have a look at the repo to understand how they ultimately did the trick.

    – NoIdeaHowToFixThis
    Jun 21 '17 at 9:31













    You are very welcome @NoIdeaHowToFixThis Until you figure out gdoc.pub, you can try adding padding or margins to the document itself. Not the greatest of choices but that's the double edged sword of Google services: free but spotty control, plus documentation is never complete because they change things often.

    – zer00ne
    Jun 21 '17 at 9:53





    You are very welcome @NoIdeaHowToFixThis Until you figure out gdoc.pub, you can try adding padding or margins to the document itself. Not the greatest of choices but that's the double edged sword of Google services: free but spotty control, plus documentation is never complete because they change things often.

    – zer00ne
    Jun 21 '17 at 9:53













    0














    There's no need to use an iframe. You can send a CORS request to GET your document in javascript using a regular XMLHttpRequest. The response is an html document which you can read, modify or render.



    See this answer for some example code: https://stackoverflow.com/a/53965010/8932511






    share|improve this answer




























      0














      There's no need to use an iframe. You can send a CORS request to GET your document in javascript using a regular XMLHttpRequest. The response is an html document which you can read, modify or render.



      See this answer for some example code: https://stackoverflow.com/a/53965010/8932511






      share|improve this answer


























        0












        0








        0







        There's no need to use an iframe. You can send a CORS request to GET your document in javascript using a regular XMLHttpRequest. The response is an html document which you can read, modify or render.



        See this answer for some example code: https://stackoverflow.com/a/53965010/8932511






        share|improve this answer













        There's no need to use an iframe. You can send a CORS request to GET your document in javascript using a regular XMLHttpRequest. The response is an html document which you can read, modify or render.



        See this answer for some example code: https://stackoverflow.com/a/53965010/8932511







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Dec 29 '18 at 15:37









        AlkisAlkis

        214




        214






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Stack Overflow!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f44518769%2fgoogle-docs-iframe-change-padding%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            kcx8qp6gxEzi3v9QQnLHhUN,Jb7NAkeAzhSwVfX1s7MZvxxoUT2BDK0Zx,NC,fC7H2ZkrF6fdc7D84ZCbCyN k A39QEHGEPL
            XpnB vD3wg7CR 4V5LWNQKxKtg DkOW5UkYmAd

            Popular posts from this blog

            Monofisismo

            Angular Downloading a file using contenturl with Basic Authentication

            Olmecas