FEATURE REQUEST: Independently zoom page size and font size

Firefox lets me zoom the page in and out, which is great, but usually useless. The problem I usually have is that font is the right size, but the text doesn't all fit in the window. What Firefox needs is a way to independently zoom text and page size. Then, I could fit all of the text in the window without making the text microscopic. Here's how it would work: CTRL+- ZOOMS JUST THE PAGE SIZE. The text size would remain the same. CTRL-SHIFT+- ZOOMS JUST THE TEXT. The page size would remain the same.
I know this is possible. The fact that Firefox can zoom the text only without affecting the page size is evidence of that. Firefox is always looking for good ideas that have never been done before. Well, this is one of them. Do it, and we would love you all forever!

Web pages with a fixed width layout will always be a problem for any zoom feature. Assuming Firefox wants to adjust the layout so it can't exceed the width of the window, should it just do a proportional adjustment of widths or try to keep sidebars the same while reducing a main area, or wrap a sidebar to the bottom of the content (as though it were a floated element), etc., etc. Maybe the experience of programming zoom on mobile browsers will feed back some learning to desktop browsers, but UI designers have a long way to go there as well.
In the short run, maybe something like the [https://addons.mozilla.org/en-us/firefox/addon/readability/ Readability extension] will help tame those unruly layouts?

Similar Messages

FEATURE REQUEST: After Effects style Placeholders and Proxies

If you feel the needs in efficient proxy workflow, welcome to the club and don't hesitate to submit feature request.
Here is the adjusted to less than 2000 symbols feature request text:
***After Effects style Placeholders and Proxies***
It would be nice if PrPro offered AE style Placeholders and Proxies workflow. There are cases, where they are extremely useful, e.g.:
1. Huge modern formats and resource hungry codecs. Not all machines can easily handle 2k or 4k footages, some can't get real time playback even with AVCHD. Not to mention that CinemaDNG importer was discontinued partly because of inability to get real time playback in PrPro. The issue can be resolved via rendering previews, but that's not always the most efficient workflow.
2. In multicam editing issues mentioned above increase dramatically. Rendering preview for every camera angle is simply impossible. Although PrPro offers offline clips workflow, an editor can't easily see if the clip is currently linked to a source footage or a proxy, and switching between sources and proxies involves several steps every time one needs to switch: selecting assets, making them offline, right-clicking again to link to other media, locating files on a disk; while in After Effects it's just one click once a proxy is set.
3. Adobe Dynamic Link. PrPro communicates with AE projects via single instance of headless AE, which creates a bottleneck and entails the need to render DI for complex comps. Although AE allows to set DIs as proxies and, hence, enjoy the best of both worlds, instantly switching between DI and dynamically linked comp and no needs to replace anything in PrPro timeline, with hundreds of dynamically linked comps PrPro timeline becomes unresponsive and takes forever to render (for my rig test 30 min sequence built out of 935 dynamically linked comps, which are just source footages in their own comps, hence, the equivalent to rendered DIs set to proxies, takes around 27 hours to render, while 30 min sequence built out of the same 935 source footages renders in real time). Meanwhile, PrPro doesn't currently allow to link offline dynamically linked comps to rendered DIs.

As the person who maintains the feature request database for After Effects, I can confirm that the number of times an item has been requested is a major factor when we consider what to work on next. So are other factors, such as how hard the feature is to implement and maintain, how much testing is involved (often the larger concern than programming time), whether the request conflicts with something else that we are already working on, and so on. It is true that we consider not just raw numbers of requests but the details of who is making the requests---e.g., whether the requests are coming from animators or compositors, beginners or experts.
I can only speak for the After Effects team, but the Premiere Pro team works much the same way (which is unsurprising, since we are in the same group and have overlapping team members).
We also try to give some visibility into the most requested items with posts like this:
http://blogs.adobe.com/aftereffects/2012/12/top-feature-requests-for-after-effects-in-2012 .html

LR3 Feature Request - Heal Preset/Import Capability and Stuck Pixels

(Note: I posted something similar some time ago but the original thread seems to be inaccessible although a cached Google version is available here. )
2 features requests but with a common theme :-
1) Spot removal/cloning/healing added to a preset. Currently the only way to do this is to copy and synchronise during an editing session of photos that have already been imported. The capability to save spot removal as a preset would be very useful for dealing with recurring dust spots and similar issues.
Which leads to request 2 -
2) The ability to manually 'tune' the hot pixel removal capability. Currently LR is failing to deal with some stuck/hot pixels on one of my cameras (a Ricoh GRD III) if this is linked to the way DNG has been implemented in the Ricoh, as suggested in the earlier thread re this subject, then a response from Adobe to confirm this would be appreciated, either way some ability to 'tell' LR what to do would be of benefit.

Thanks for the response Rob, saving a 'target' image is a good idea, but other than that I don't see this workaround as being particularly different from the approach I outlined in my initial post. One of the most useful capabilities LR has is being able to apply presets during import, yet Adobe for whatever reason have not allowed any of the tools (other than graduated filters) to be applied this way, I would love to know why. There was a 'bug' with LR 1 if I remember correctly whereby spot settings could be saved to a preset, but this was 'fixed' in a later release, so it appears to be possible to implement this functionality, yet they have decided not to do so.

Feature Request: Setting App page title to something other than "Eloqua 10"

Hello everyone,
Long-time lurker, first-time poster. As someone who has been using Eloqua for over 3 years, when working in the application, I will usually end up with upwards of half-a-dozen tabs open in Firefox, all of which say "Eloqua 10". Because of this, I'll usually try to strategically organize my tabs, but often times I end up having to click through multiple tabs to find the one I'm looking for, which can sometimes lead to Firefox freezing. I'm sure I'm not alone in this.
So to alleviate this, I'd like to make the following feature request: Can we have the tabs/windows named by Asset Type & Asset Name? Perhaps in the following Format:
[Asset Type]: [Asset Name] - Eloqua 10
Note how I have "Eloqua 10" at the end of the string. An example of a title would be: "Campaigns: Nurture_Campaign_1 - Eloqua 10"
Could this please be implemented?
Thank you,
Sean

Here is a snippet of code that I wrote and use without any problem:
   public void ppPrint() {
      if (printJob==null) initPrintJob();
      try {
         if (!printJob.printDialog(aset)) return;
      } catch (Throwable e) {
   public void initPrintJob() {
      aset=new HashPrintRequestAttributeSet();
      aset.add(new JobName("AOKabc",null));
      aset.add(new MediaPrintableArea(.75f,.25f,7.5f,10.5f,MediaPrintableArea.INCH));
      printJob=PrinterJob.getPrinterJob();
/* locate a print service that can handle the request */
      PrintService[] services=PrinterJob.lookupPrintServices();
      if (services.length==0) System.out.println("Warning: No printer detected!");
      else {
         try {
            printJob.setPrintService(services[0]);
         } catch (Throwable pe) { }
      pageFormat=printJob.defaultPage();
      Paper paper=new Paper();
      paper.setImageableArea(54,18,540,756);
      pageFormat.setPaper(paper);
      printJob.setPrintable(Preview.this);
   };o)
V.V.

Feature Request - CSS code generation for advanced font - type options

Thanks to everyone for the amazing work done in Photoshop and Illustrator to enhance the ability to generate and use character and paragraph styles translated to CSS. The last two releases have brought designers something they could only dream of and talk about for the last decade, and now these tools are being delivered!
This request is to consider being able to use advanced character styles in Illustrator, such as X/Y percentage height/width of fonts, rotation or baseline shift to generate CSS for these options. As of this post, I haven't been able to find that CSS3 even supports these options, except possibly the 'font-stretch' rule, which does not appear to be supported yet in most browsers - see CSS Fonts Module Level 3 - W3C Candidate Recommendation, October 2013.
Sometimes, designers get very picky about wanting type to look just so, including making fonts look taller or wider in a design, although perhaps much to the horror of the original type designer
thanks very much,
Mark

I'll also add this is a feature that should be carried over into Adobe Photoshop too.
Within Adobe Photoshop if you want to size type in terms of pixels the type is, again, sized according to the Em square. Unless you're setting type at pretty large pixel sizes the rendered type really ends up looking pretty bad. That's because the edge of the baseline and the edge of the cap height line are never aligned to the pixel grid. You end up with type that's fuzzy looking on all sides. If designers were able to tell Photoshop "make this lettering 20 pixels tall according to the capital letters" the lettering would looking a whole lot better. Perfectly crisp edges on the base lines and cap height lines.

Feature Request: Song Controls in Coverflow and Bigger touch buttons

Something that really needs to be added to the iPhone software for the iPod are song controls ( |<< and >>| buttons) when the phone is resting sideways and in coverflow mode. I use the iPhone in my car as an MP3 player, and if it is in coverflow mode and I am listening to an entire Genre (on shuffle), there is no way skip forward to the next song - this also becomes a problem if I'm using an armband. It would be nice if Apple added forward/backward skip buttons in the coverflow mode.
Also - another concern is that touch-area around the song control buttons when you are NOT in coverflow mode isa bit small. When you are driving in a car, it actually becomes difficult to find the right area to touch (you know the >>| button) to skip to the next song. These would benefit from a small increase in size or just the touch area surrounding the button.
These seem like simple changes that can be easily implemented. Anyone else have these same concerns? Does anyone else have any other simple features that could be added to the iPod functionality to make it easier to use?
Message was edited by: dpbeardsley

Since this is a user to user help forum only for technical support issues and questions, best to use the iPhone feedback link for such feedback, which at least ensures that your feedback is forwarded to and read by the appropriate Apple personnel but does not ensure that your request will be implemented.

Feature request / Add blank pages

Hey!
I'm using the Adobe Reader for Android on my Samsung Galaxy Note 10.1 2014 Edition since about one year and i'm very satisfied with it!
But there is thing i'm missing meantime!
I would like to add blank pages to a pdf document!
Is there a way to add a feature like this in one of the next versions?
Thanks for answer!

We have noted down your request and would forward the same to the Product Management. However, we cannot commit if this would be available in the immediate future.
Thanks,
Adobe Reader Team

Feature request: better tools for commenting and editing text

We currently use a comments-enabled Acrobat workflow with InDesign to track changes to our large catalog project. Was hoping to move our team over to CS Live, but currently the commenting tools are sub-par, and not accurate enough for extensive text editing. My request would be to imitate the text editing functionality of Acrobat:
In CS Live online:
- allow users to be able to copy selected text. (This is useful when a reviewer wants to be able to modify a sentence or paragraph. It's a headache now to have to retype the sentence prior to making modifications)
- Ability to highlight text and hit "delete" to mark text as deleted, or highlight and type over to indicate replaced text
- Ability to click to insert text, and have the comment appear with the inserted text designation (little blue carat like in Acrobat)
- ability to highlight a section of text
In InDesign:
- ability to copy the text in a comment and NOT copy all the other extraneous meta data. (Currently, if you click "copy text", it will copy the comment along with all the details about the comment. For example, "- Amy Stewart [10.06.11 at 12:56 PM]"
- ability to see in InDesign the EXACT part of the text that needs to be modified. Right now, the red box outlines the general area. The CS Review panel shows a tiny thumbnail with black highlight over the area of text that needs to be changed, but unfortunately, there's no way to zoom in on it, so you're stuck having to toggle between InDesign and the online review, where it's possible to zoom. (This diminishes the utility of the CS Review panel.)
If you were able to incoroprate all the commenting functionality of Acrobat, I think you'll have a winner. But right now, we're going to have to stick with Acrobat as it's the only way to easily modify text.

Sorry if I might be stating the obvious (but at least I was such a *dummy* once that I needed this explicitely):
In order to move the sequence of images per drag&drop in grid view you need to
Put the sort order in the bottom toolbar to "user order" (toggle visibility with letter T if not displayed)
Grab an image from within its thumbnail, not from its border-cell.
When you move around you see a vertical black thick line wandering in between images where you would be able to drop it
Put the images first into a collection in case they should be spread across multiple folders.
This is the reason why most often from a filter result you cannot re-arrange.
Still sometimes it does not work as I want, but can *be persuaded*, i.e. I repeat the same trial after first moving to another collection, then return back. I can't nail it down sufficiently to file a bug.
For an automated sorting according to filename (chosse that setting finally in toolbar) you could rename the photos in place, without exporting & re-importing. Just select them and hit <F2> to bring up the renaming dialog like possible during import.
+1 vote from me, as I am neither satisfied with the responsiveness of moving folders within LR e.g. from laptop hard disk to NAS.
Apart from that I try not to build much on my folder structure, just break them into manageable quantities and have a quick "diary-overview" by using naming convention "YYYY-MM-DD description of event" (pictures of up to 4 cameras go inside, unique filenames for Canons achieved by renaming during import). For all the rest I prefer to build (smart) collections.

New feature request - More Zoom Levels at a Keystroke

Hi
I would love to have more levels of zoom available at a keystroke
I just took an image into Photoshop CS 5 from LR (I bet the developers hate this comparison - there must be considerable, if friendly rivalry in Adobe!) and remembered the joy of just hitting the "+" key maybe three or four times and then the "-" key till I have the image at the right size I want it and then throwing the image about with the hand tool in that way so that the image carries on after you let go (I can't remember what that is called -anyone help me?). It just seems much quicker and more intuitive than LR which lets you have one quick level of zoom and doesn't have that easy moving around of the image which PS has.
I suspect that problem for developers in being able to do this in LR could be to do with the way that LR deals with previews and the fact that it probably has to load and compute any adjustments you have already made to the image before it can even give you a fully rendered image at any given size.
Any feedback from LR developers or other people who agree with me would be much appreciated
Steve
PS Tried again to use http://feedback.photoshop.com/photoshop_family but keep getting 'Password is invalid' message when I try to post even though I have just signed in successfully. Nightmare.

Hydephoto wrote:
I suspect that problem for developers in being able to do this in LR could be to do with the way that LR deals with previews and the fact that it probably has to load and compute any adjustments you have already made to the image before it can even give you a fully rendered image at any given size.
Any feedback from LR developers or other people who agree with me would be much appreciated
It would be more than useful but I don't know if it's the previews or not. You compared with PS but even with C1s workflow the zoom works as you'd expect and pretty fast too. I'm sure Eric will give the scoop as to why LR handles it in this way.

Feature request: Support for {table abbr} and {table} in Table scripts

Hi Data Modeler Team,
support for {table abbr} and {table} in table scripts ("Table properties"->"Scripts"->All four tabs) would be greatly appreciated as it makes it easier to use boilerplate SQL in these areas.
Is it possible to add this feature to one of the upcoming releases?
Thank you,
Blama

Hi,
I've logged an enhancement request on this.
Thanks,
David

Pages app and fonts

Finally broke down and purchased Pages for the iPad. Decent app as farvasbit goes.
My question: is there any way to add fonts to it? an app maybe? existing fonts don't match up all that well to the MS Word docs I use from the office.

From a previous post that discusses adding font to Keynote:
Unfortunately, no. Fonts on iOS are predefined. Custom fonts are defined by the app and are application specific. Short of you modifying the Keynote app bundle (which would break it), you can't add your own fonts.

Feature request: smooth zooming in develop module

It would be very helpful if the develop module (especially) allowed viewing not just at 1:1, 2:1, 3:1 etc but also at every % in between.
This would make it far easier to properly evaluate the image at output size where you intend to upsize (or down sample) on output. For example, some of my stock libraries require a standard size which isn't the same as sensor size.
Is this a possibility for LR3?
Thanks,
David.

johnrellis wrote:
Doesn't catalog:getTargetPhoto () return just one photo, the active photo?
Yes, but the problem is that a develop-settings plugin (as example) should target all selected photos in grid view, but only most selected photo in loupe and develop modes - in order to be consistent with how Lightroom proper behaves, which is what most users expect. At present there is no way to do it - that I can see. Its not a big thing as long as the users understand what behavior to expect, and in fact I think I'll just put a checkbox for "all selected photos" vs. "most selected photo only" right on the interface which will make it clear and give either option regardless of display mode / module - I think this will be a super solution actually - thanks for helping me think of it .
Rob

Feature Request: Useful toStrings in Cookie and HttpServletResponse/Reques

Hi. It seems obvious to me that the Cookie.toString() should give the text representation of the Cookie as it will appear in the HTTP header. The reason that I need this is that Java does NOT support HttpOnly and I need to insert it into the Cookie manually. I can do this somewhat using HttpServletResponse.setHeader(java.lang.String name, java.lang.String value) except that I have a complex application with Cookies being set multiple times and there is no HttpServletResponse.getHeader(java.lang.String name) to allow me to read what'[s in the SET-COOKIE header, dynamically change it and write it back.
A reasonable implementation of HttpServletResponse.toString would allow me to do what I need to do also, but that alas also just shows the reference.
HttpOnly will not be the last custom HTTP cookie attribute or HTTP header and Java should give better support for dynamically managing HTTP headers.
I think that toStrings are a great idea, but it seems that as a general rule, useful toStrings have not been implemented in the Java libraries.

I would post the request here:
http://bugs.archlinux.org/

Request for a page *explicitly*, and in text, stating ESR 10x End of Life - please create one - thanks!

Please create a page/wiki-entry/blog-post/whatever explicitly stating End of Life for ESR 10x branch.

The 10.0.12esr is no longer listed on http://www.mozilla.org/en-US/firefox/organizations/all (used to be more on bottom with 17.0.2esr on top then) since it is EOL.
https://blog.mozilla.org/meeting-notes/archives/1261 (January 10, 2013)
Firefox 10.0.12esr (our final planned 10-series ESR) and Firefox 17.0.2esr were both released yesterday

Feature Request: save metadata to file, and read metadata from file.

Please have function to save metadata to file, and read metadata from file.
This would allow us to write cross-platform plugins that can assure data is up-to-date in the xmp, or modify xmp and have it reinstated in the catalog.
This would go nicely with the ability to save xmp for virtual copies, dng, and rgb formats.

Perhaps someone with direct experience with publishing to Smugmug will chime in. Short of that, some thoughts on your issues:
Should I not bother to "Save Metadata to File", this seems to be what is messing up the SmugMug publish service?
I very much doubt that it is messing up the publishing. What gets saved to the file from the catalog is independent of what gets exported. Saving metadata to the file is generally a good practice (in case you screw up your catalog backups). Many, perhaps most, users set the preference Catalog Settings > Automatically Write Changes Into XMP.
I would have expected it to behave like an export which would write synonyms, exclude keywords that should be excluded, etc, which seems to work ok in point 6 above.
Yes, that's a reasonable expectation.
You may have done this already, but double-check: Right-click the Smugmug publishing service in the left-hand column of the Library, select Edit Settings, and in the Metadata section verify that you have Include: All Metadata set.
Did you download the Smugmug plugin from Smugmug? You might try this Smugmug plugin instead -- the author designed the publishing architecture of LR and has an excellent reputation.
Are the publish services more effort than they are worth? So I get SmugMug to work, what happens when I try Flickr?
I think many users find the publishing services are generally worthwhile. I publish regularly to Flickr (using the built-in Flickr plugin, which isn't completely reliable) and the Zenfolio plugin from Friedl.

FEATURE REQUEST: Independently zoom page size and font size

Similar Messages

Maybe you are looking for