I have a page which is generated by the CGI script. And there the image jumps down, after it is shifted to the left. I have saved the HTML code of the page and stored it as new document on the server. And then it doesn't jump.
Related
I'm working on a documentation site and noticed that the images have a very slight delay. I realized it's because the alt text shows up before the image renders.
Is there a way to hide the alt text before the image appears?alt-text-shows-up
I want the image load to look a little cleaner to the users. If there's something that I could do on my end it would be appreciated. In the docusaurus blog I noticed the same thing happens with the image, I see the alt text before the image appears https://docusaurus.io/blog
At first I thought it was just on my end, but my peer noticed it on his machine as well.
I had the images in a folder with the .md document, then moved them to the static folder as it was suggested on the docusaurus website. The delay still persists even when moved to the correct folders.
I am using BIDS to develop a report that needs to be configured in one page when viewed on the internet explorer but still needs page breaks for good display in PDF when exported. The problem is that when i insert page breaks beetween tables another page is added to the report and i only want that in the PDF. Is there any way i can insert page breaks in the PDF but not on the report view itself?
You can achieve this by setting the InteractiveSize property to the wanted value (0 can be used to make it infinite).
If you wish to keep the same width, then you should only change the Height.
Edit: Defining specific page breaks will always force the viewer to use paging as well. This was implemented to improve the performance of large reports to allows users to begin viewing the initial pages of the report while waiting for additional pages to become available.
HTML and Excel output shows a report as a single page if there are no
page breaks. If you do specify InteractiveHeight and InteractiveWidth,
the HTML and Excel output formats render reports using soft page
breaks. Soft page breaks are placed on a page using an estimated page
size, which makes the size of the reports less exact than reports
produced by an output format that supports page size. Soft page breaks
are calculated at run time by the control. Although it is not
recommended, you can disable soft page breaks by setting
InteractiveHeight to 0.
Source: Defining Page Size and Page Breaks in a ReportViewer Report
As described in the quote above, the InteractiveHeight is used to apply soft page breaking when using the report viewer. So the solution is to only use soft page breaks.
You can manipulate your report to break correctly with paging without using hard page breaks by wrapping the wanted blocks inside rectangles. These rectangles you then re-size to be the size of a page and set the property KeepTogetheras true.
This will try to fit the content of the rectangles on the same page, adding a break when you reach the next rectangle. Because your InteractiveSize has no limit, this will not be displayed in the report viewer.
I am using Selenium with PhantomJS to scroll to the bottom of an infinitely scrolling page of Twitter search results.
driver.execute_script("window.scrollTo(0, document.body.scrollHeight);")
I manually set a number of times for it too loop (I try to estimate how many reloads the web driver can take before crashing). When done, I grab the raw html:
text_file.write(driver.page_source.encode("utf-8"))
This works ok, but I am looking for a way to keep the program going without the 'browser cache', or whatever it is called, filling up. Any ideas on how to achieve the steps below?
Run the driver.execute_script("window.scrollTo(0, document.body.scrollHeight);")command for X times
Then dump the loaded raw html to a text file
Then run the driver for X times again
Then dump the loaded raw html into another text file, but not the content loaded in step 1, only the new content loaded in step 3
This would empty the browser/driver memory into several output text files and make it possible for the loop to practically go on forever. Any ideas?
I'm still new to coding. I downloaded flex slider, and I have it running fine on my site and working fine. However I can't make ANY edits into my html regarding the slider. It has the 'next' and 'previous' image links on my gallery, which I would like to replace. It shows up in the html when I inspect it in firebug, yet when I run my html through my text editor (Im using text mate), it doesn't show up at all!
Any ideas why?
I think you are talking about the navigational arrows on the left and right side of the images. This can be changes in the "flexslider.css" file. If you are using textmate then the line number is 52.
Probably the easiest way is to find the image here images/bg_direction_nav.png. Right click the image and open with your image editing software eg. photoshop. Then once you have change the image just save it and it will be saved in the same folder location. If you keep the image the same size then you will not have to mess around with anything else..
I need to set the margins differently for the first page than the rest of the pages.
I've messed around with inserting section breaks (as from what I've read is that Word creates a section break when you choose to apply "this point forward" from the Page Setup Margins tab, but I can't seem to consistently create a continuous section break at the start of the second page.
If not section breaks, any other way would be fine. Need to adjust margins to match new letterhead design for a bunch of existing documents so am planning on fixing the margins in a sub-routine when the print button is clicked (part of another macro).
A Continuous Section Break is used to allow multiple sets of margins within the same page. A Next Page Section Break, which has the properties of both a section break and a page break, will allow one set of margins for the first page and another set of margins for all pages following it. One way it can be created is like this:
Selection.InsertBreak Type:=wdSectionBreakNextPage
Now here's where it gets tricky. Word has two different types of page breaks: Automatic and Manual. Automatic page breaks get created when text no longer fits on a page and Word automatically generates a new page. If the documents you are reformatting via the macro have automatic page breaks, inserting the Next Page Section Break at the end of the first page will cause Word to delete its Automatic Page Break (using the Next Page Section Break to keep the pages separate) and any margin changes you make to the first page will not carry over to the following pages. However, if the documents contain a Manual Page Break between pages one and two, inserting the Next Page Section Break will create a blank second page. As such, if this is a possibility, code will need to be written to detect the Manual Page Break and delete it after the Next Page Section Break has been inserted.
Letterhead layouts and Word can be really difficult and tricky if you need other values only on the first page. In my practice, I find often letterheads with graphical elements in a right margin of the first page up to a certain heigth, e.g. a list of partner names or business information. So on the first page the right margin should be 6 cm, while on all following pages it should be 2,5 cm.
Using a section break is not possible due to the fact that it moves while the user inserts text.
I've used the following approach with some success:
Create a text box in the first page header which is sufficiently big to occupy the space needed. Setup the property for "Text Wrapping" = Square, so that text cannot overlap the box.
Of course you can insert the text box also into the document body to have that effect. Unfortunately, users can then touch the text box easily in a mouse action, and move it to another position. If you put it into the first page header, it will appear only on the first page, and will appear "in the background" of the page. The user can enter text in the document body, but it will stop before the text box, which simulates a right margin on the first page.