Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 3 years ago.
Improve this question
I'm viewing a non-secured (i.e. no passwords applied for any option) pdf file in acrobat Pro 11.
I'm viewing the file at 144% magnification/zoom level. But whenever I click another bookmark (from bookmarks panel) or another page (from pages panel), the zoom is reset to full page (or whatever is set in 'Initial View' tab of the Document Properties dialouge. How can I avoid this. I mean, I want that whenever I navigate to other page or bookmark, the zoom shouldn't change to any other than whatever the current zoom percentage is.
I found a circumvention: Use the free Foxit PDF Reader (https://www.foxitsoftware.com/products/pdf-reader/)
As I type this, I'm running version 7. In Preferences > Page Display, select Forbid the change of the current zoom factor during execution of 'Goto destination' actions...
I tested this with a PDF that was annoying the heck out me by changing my preferred zoom factor every time I clicked a bookmark. The free Foxit Reader blocked bookmarks from changing the current zoom level.
I also have Adobe Acrobat. Although it is in theory a full-featured PDF editor, it doesn't provide any straightforward way to reconfigure the PDF's bookmarks Zoom level: fit page setting.
Using Foxit Reader doesn't fix the PDF's unwanted bookmark behavior. But it does enable one to view a PDF without having to constantly put the zoom value back where one wants it after clicking a bookmark...
Hey, the problem was troubling me too much and in the end I could SOLVE the same (google didn't help).
First, I had tried changing the settings properly at two places, in Adobe Preferences> Page Display. And in File Properties> Initial View. But still when I clicked any bookmark, it zoomed back to 'Fit to Page'.
What solved my problem, in the end, is that I selected any/all bookmarks (Ctrl+A) in the bookmarks palette, and then clicked the bookmarks palette menu (on the top left side of bookmarks palette)> Properties> Actions tab and there deleted (or edited) the actions present.
That's it. Thank you guys for your lovely answers ;)
Every time I opened the PDF, it zoomed to "Fit width." Also, after opening, I could set the zoom to whatever I wanted and everything was fine unless I scrolled to the very top of the document where it would again zoom to "Fit width."
I tried adjusting document properties, Acrobat preferences, even bookmark properties (bookmarks can specify zoom level instead of just saying "Inherit").
Finally, I switched the navigation panel from Bookmark to Page view. Right clicked on the first page icon and checked properties. There was a "Fit width" zoom setting that executed on "Page Open". I deleted that action and have had no problems with that file since.
I've changed an editable PDF's bookmark-zoom behavior as follows:
Download and Install JPDFBookmarks
These download links valid as of 24 April, 2019:
http://codebyjoshua.blogspot.com/2012/02/easily-change-pdf-zoom-level-and-name.html
http://sourceforge.net/projects/jpdfbookmarks/
Open the PDF in JPDFBookmarks
In a PDF editor such as Acrobat, modify one of your bookmarks to have the type of zoom you want. This enables you to copy the desired zoom settings in subsequent steps.
In PDFBookmarks, open the zip file, extract the files, then open the PDF file JPDFBookmarks.
Dump the bookmark data to a text file using JPDFBookmarks with the command Tools > Dump.
Find/Replace the Bookmark Settings
Open the PDF dump file in a text editor, then find the bookmark you edited.
Find/Replace the bookmark settings:
a. Copy the correct portion of the text associated with your edited bookmark that is different from all the other bookmarks. For example,TopLeftZoom,0,0,0.0.
b. Find/Replace the other setting on all the other bookmarks, such as FitWidth, -6.
You can change the name of any bookmark while you're here.
Save the changes to the text file.
In JPDFBookmarks, load the bookmark data back using Tools > Load
In JPDFBookmarks, save the file as a modified version of the original PDF.
The bookmark zoom behaviors have been fixed.
Related
In Visual Studio Code, there was previously a trash image (icon) in the panel section. When I clicked on it the terminal was clearing. But it no longer exists. I changed accidently panel settings. For solving, I clearing settings.json folder but still same. Why does it never revert back to its old settings?
The Trash-bin Icon is Still Very Much Present in Your Editor
"The other solutions here, though no wrong in what they say, are not good solutions. The icon is still present if you know where to look, and you didn't accidentally change your settings. In the last VSCode update — "the May-2021 Update (v1.57.1)" — the VS-Code team added support for the new feature, "Terminal Tabs", which does more than add terminal-tabs, it offers users an entire new UI to use. It also switched the configurations of millions of unexpected VSCode users, so that the new UI was auto-equipped. In all fairness you are not the first person to wonder where the "Trash-bin Icon" went. I answered another question, 2 weeks ago, asking about the drop-down that is no longer visible."
You have two options available to you.
You can, keep the new UI the way it is, and below is a picture that shows where the new terminal tab trash-bin icon is.
Or you can switch back to the old UI using the setting bellow:
terminal.integrated.tabs.enabled: (true/false)
Image shows "terminal.integrated.tabs.enabled": false, and where the trash icon is. It is important to note that the icon auto hides, and one must scroll over it before it reveals itself.
Image shows "terminal.integrated.tabs.enabled": true, and where the trash icon is located using the old UI. I think its fair to note, the new UI was created to make VSCode better. People use to download extensions to get the same terminal tabs that the new UI offers.
I am improving the accessibility of a website to make sure users can easily navigate using the keyboard only. There is a button that generates a file, but after clicking on the button, the generic browser download dialog appears at the bottom of the page, and the focus still stays on the button. Users with a screen reader are not notified about the dialog.
There is a way to focus on the dialog when it appears?
I am able to focus on elements of the page, but since the dialog is a browser feature, I have no idea how to do it!?
I will appreciate any guidance what can you give me. Thank you!
You do not have control to do this, plus this is expected behaviour and there is nothing you need to do.
Screen reader users will go out of the active screen using shortcut keys if they wish to access the file.
Other considerations as you said "button" in your question
You should not use a <button> element to generate a file. File downloads should always be a hyperlink (<a>).
If the document requires variables to be passed and you are able to pass them via a GET request then the hyperlink href should be the URL + GET parameters.
The advantage of this for everyone is that they can middle click to open the document in a new window (or right click and choose "open in new window" etc.), plus it works without JavaScript and is easily indexed by Search Engines.
Also adding the download attribute to a hyperlink has some advantages, especially as in some screen readers it gets signalled to users that this link will download a document.
When creating a download link you should state the document type (pdf, word etc.) and document size for accessibility. You can do this with visually hidden text if your design does not allow for it.
I have written a reasonably in-depth answer on how to add the file size and file type info for screen readers here. About 70% of it is relevant to you.
I am developing a chrome extension. When I install it one of its icon is displayed in address bar. I want that icon should not be displayed after installation.
Starting with Chrome 49 (see the announcement and detailed description) all extension icons are displayed in the browser toolbar:
[...] each extension the user has installed has a persistent UI surface. By default, this will be in the toolbar to the right of the omnibox (where browser actions are now), and the user can choose to hide ("overflow") these actions in the Chrome menu.
The reason for this is to protect our users. We've heard too frequently that many users are unaware of the extensions they have installed, whether this is due to sideloading, installation by phishing, or simply the user forgetting how many and which are installed. Unfortunately, extensions consume computing resources, and may have significant security, privacy, and performance impacts. Because of this, we've decided we need to increase user visibility.
What this means for your extension:
If the extension has a browser action: Nothing! (Apart from the slightly different hide/overflow functionality.)
If the extension has a page action: The extension will be given a persistent icon in the toolbar. On pages where the extension's page action wouldn't normally be visible, the action will be greyed out, indicating that it doesn't want to act. On pages it does want to act, it will be fully-colored.
If the extension has no action: Similar to page actions, the extension will be given a persistent icon in the toolbar. It will be shown with the greyed-out look all the time.
Displaying the action persistently, even in the cases of a previously hidden page action or an extension with no action, is necessary because the presence of an action doesn’t always correlate with the extension acting. We also can’t show the action conditionally on, e.g., a per-tab basis, because there are many actions that are not correlated with any tab. In order to ensure users are aware of the extensions they have installed that could be affecting their browser, we need to ensure each extension is visible.
We've done our best to limit the functionality this breaks, and hope you understand the trade-off between developer inconvenience and user benefit. Thank you for understanding as we keep our users safe!
An end user of your extension may manually hide the icon either by adjusting the overall toolbar width (click the space between addressbar and toolbar and drag) or by rightclicking an icon and selecting Hide or Show:
I want to debug code at the same time as I see what is being sent on the network tab without having to go back and forth between the Network tab and Sources tab. Is there a way to do this as of chrome Version 52.0.2743.82 or Version 54.0.2810.2 canary?
I know that it is possible to log http request in the console which can be visible with other tabs open but I want the actuall networks tab if possible..
Thank you in advance
This is now possible in Chrome 87. Right click Network in the menu and select "Move to bottom"
and it will do this
You can view 'Quick source' while viewing the Network panel (or the other main panels) at the same. This will allow you to view the source and add breakpoints.
However, it's not possible to step through code using the debugging in the split view. Chrome will automatically switch to the Sources tab if you use the shortcuts.
It's also not possible to have an extension running a separate instance of the debugger as the Chrome Debugging Protocol doesn't allow simultaneous clients to be connected.
I will open up a discussion with other Chromium contributors into the feasibility of sharing the debugging controls in the split view. I don't know whether it will or can be done easily. I suspect it's a fair amount of work.
If you would like to set up the split view, as it's useful anyway, go to overflow menu on the right side and select 'More Tools' and then select 'Show console'. This makes sure the panel loads below the main one.
On the left side of the panel that shows, click the overflow menu and select 'Quick source'.
You will now see a small Sources panel.
Since I was referred here from this question, I'll answer here.
In my scenario I need to be able to work on two different source files (under DevTools->Sources) simultaneously, for instance an html and a css file.
My workaround was to work on two separate tabs.
Right click one of them and click 'Open in new tab'.
When the new tab is open press F12 to open DevTools, and dock the two editors side by side (Focus on one and pressing ⊞+→ then leftwards on the other one).
Result:
Is there any way to completely duplicate the state of a current tab in Google Chrome? I want an exact copy of the current state of the page without having to reload the page in another tab.
An example use case:
While browsing a "slideshow" on a news website, I want to preserve the current slide that I'm on, but create a duplicate so that I can continue viewing the next slide. If I simply Right-Click and "Duplicate" the tab, the new page will completely Reload, reprocessing all of the Javascript and running the pre-slideshow advertisement again.
In short "NO" you can't.
I am not expert on this
but a similar behavior can be achieved in some ways i know :
Dump the whole DOM
Never tried this though. You can convert the DOM to a string, pass it to the new window and then parse it as a document. This will let you lose your DOM events and State manipulation javascript. (But that's good for your case)
var dtab = window.open('about:blank', 'duplicate_a_tab');
dtab.document.open();
dtab.document.write("... yout html string ..");
dtab.document.close();
Develop an extension
Let the users continue on the current tab with the current state, your extension should be able to capture the screenshot of that area and open that screenshot in new tab. There are plenty of screenshot taking extensions are available in the market.
If that website is your own
You can develop your services that uses state locally like progressive web apps. Give a link separately to 'duplicate' which will eventually open the same URL in different tab with the same local state and with the flag do-not-sync.
This will not work when the user uses browser inbuilt duplicate
feature.